麒麟V10的操作系统,启动redis报错

启动redis报错,


1:M 31 Oct 2025 02:53:56.029 * <bf> 	{ bf-initial-size     :       100 }
1:M 31 Oct 2025 02:53:56.029 * <bf> 	{ bf-expansion-factor :         2 }
1:M 31 Oct 2025 02:53:56.029 * <bf> 	{ cf-bucket-size      :         2 }
1:M 31 Oct 2025 02:53:56.029 * <bf> 	{ cf-initial-size     :      1024 }
1:M 31 Oct 2025 02:53:56.029 * <bf> 	{ cf-max-iterations   :        20 }
1:M 31 Oct 2025 02:53:56.029 * <bf> 	{ cf-expansion-factor :         1 }
1:M 31 Oct 2025 02:53:56.029 * <bf> 	{ cf-max-expansions   :        32 }
1:M 31 Oct 2025 02:53:56.029 * <bf> ]
1:M 31 Oct 2025 02:53:56.029 * Module 'bf' loaded from /usr/local/lib/redis/modules//redisbloom.so
1:M 31 Oct 2025 02:53:56.031 * <search> Redis version found by RedisSearch : 8.2.2 - oss
1:M 31 Oct 2025 02:53:56.031 * <search> RediSearch version 8.2.5 (Git=222ad3b)
1:M 31 Oct 2025 02:53:56.031 * <search> Low level api version 1 initialized successfully
1:M 31 Oct 2025 02:53:56.031 * <search> gc: ON, prefix min length: 2, min word length to stem: 4, prefix max expansions: 200, query timeout (ms): 500, timeout policy: return, cursor read size: 1000, cursor max idle (ms): 300000, max doctable size: 1000000, max number of search results:  1000000,
1:M 31 Oct 2025 02:53:56.031 * <search> Initialized thread pools!
1:M 31 Oct 2025 02:53:56.031 * <search> Disabled workers threadpool of size 0
1:M 31 Oct 2025 02:53:56.031 * <search> Subscribe to config changes
1:M 31 Oct 2025 02:53:56.031 * <search> Enabled role change notification
1:M 31 Oct 2025 02:53:56.032 * <search> Cluster configuration: AUTO partitions, type: 0, coordinator timeout: 0ms
1:M 31 Oct 2025 02:53:56.032 * <search> Register write commands
1:M 31 Oct 2025 02:53:56.032 * Module 'search' loaded from /usr/local/lib/redis/modules//redisearch.so
1:M 31 Oct 2025 02:53:56.032 * <timeseries> RedisTimeSeries version 80200, git_sha=1439d4a439ca9c063e6ef124a510abff09a5d493
1:M 31 Oct 2025 02:53:56.032 * <timeseries> Redis version found by RedisTimeSeries : 8.2.2 - oss
1:M 31 Oct 2025 02:53:56.032 * <timeseries> Registering configuration options: [
1:M 31 Oct 2025 02:53:56.032 * <timeseries> 	{ ts-compaction-policy   :              }
1:M 31 Oct 2025 02:53:56.032 * <timeseries> 	{ ts-num-threads         :            3 }
1:M 31 Oct 2025 02:53:56.032 * <timeseries> 	{ ts-retention-policy    :            0 }
1:M 31 Oct 2025 02:53:56.032 * <timeseries> 	{ ts-duplicate-policy    :        block }
1:M 31 Oct 2025 02:53:56.032 * <timeseries> 	{ ts-chunk-size-bytes    :         4096 }
1:M 31 Oct 2025 02:53:56.032 * <timeseries> 	{ ts-encoding            :   compressed }
1:M 31 Oct 2025 02:53:56.032 * <timeseries> 	{ ts-ignore-max-time-diff:            0 }
1:M 31 Oct 2025 02:53:56.032 * <timeseries> 	{ ts-ignore-max-val-diff :     0.000000 }
1:M 31 Oct 2025 02:53:56.032 * <timeseries> ]
1:M 31 Oct 2025 02:53:56.032 * <timeseries> Detected redis oss
1:M 31 Oct 2025 02:53:56.032 * <timeseries> Enabled diskless replication
1:M 31 Oct 2025 02:53:56.032 * Module 'timeseries' loaded from /usr/local/lib/redis/modules//redistimeseries.so
1:M 31 Oct 2025 02:53:56.033 * <ReJSON> Created new data type 'ReJSON-RL'
1:M 31 Oct 2025 02:53:56.033 * <ReJSON> version: 80201 git sha: unknown branch: unknown
1:M 31 Oct 2025 02:53:56.033 * <ReJSON> Exported RedisJSON_V1 API
1:M 31 Oct 2025 02:53:56.033 * <ReJSON> Exported RedisJSON_V2 API
1:M 31 Oct 2025 02:53:56.033 * <ReJSON> Exported RedisJSON_V3 API
1:M 31 Oct 2025 02:53:56.033 * <ReJSON> Exported RedisJSON_V4 API
1:M 31 Oct 2025 02:53:56.033 * <ReJSON> Exported RedisJSON_V5 API
1:M 31 Oct 2025 02:53:56.033 * <ReJSON> Enabled diskless replication
1:M 31 Oct 2025 02:53:56.033 * <ReJSON> Initialized shared string cache, thread safe: false.
1:M 31 Oct 2025 02:53:56.033 * Module 'ReJSON' loaded from /usr/local/lib/redis/modules//rejson.so
1:M 31 Oct 2025 02:53:56.033 * <search> Acquired RedisJSON_V5 API
1:M 31 Oct 2025 02:53:56.033 # Fatal: Can't initialize Background Jobs. Error message: Operation not permitted
Starting Redis Server
1:C 31 Oct 2025 02:53:59.757 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 31 Oct 2025 02:53:59.757 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 31 Oct 2025 02:53:59.757 * Redis version=8.2.2, bits=64, commit=00000000, modified=1, pid=1, just started
1:C 31 Oct 2025 02:53:59.757 * Configuration loaded
1:M 31 Oct 2025 02:53:59.758 * monotonic clock: POSIX clock_gettime
1:M 31 Oct 2025 02:53:59.758 * Running mode=standalone, port=6379.
1:M 31 Oct 2025 02:53:59.758 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 31 Oct 2025 02:53:59.759 * <bf> RedisBloom version 8.2.3 (Git=unknown)
1:M 31 Oct 2025 02:53:59.759 * <bf> Registering configuration options: [
1:M 31 Oct 2025 02:53:59.759 * <bf> 	{ bf-error-rate       :      0.01 }
1:M 31 Oct 2025 02:53:59.759 * <bf> 	{ bf-initial-size     :       100 }
1:M 31 Oct 2025 02:53:59.759 * <bf> 	{ bf-expansion-factor :         2 }
1:M 31 Oct 2025 02:53:59.759 * <bf> 	{ cf-bucket-size      :         2 }
1:M 31 Oct 2025 02:53:59.759 * <bf> 	{ cf-initial-size     :      1024 }
1:M 31 Oct 2025 02:53:59.759 * <bf> 	{ cf-max-iterations   :        20 }
1:M 31 Oct 2025 02:53:59.759 * <bf> 	{ cf-expansion-factor :         1 }
1:M 31 Oct 2025 02:53:59.759 * <bf> 	{ cf-max-expansions   :        32 }
1:M 31 Oct 2025 02:53:59.759 * <bf> ]
1:M 31 Oct 2025 02:53:59.759 * Module 'bf' loaded from /usr/local/lib/redis/modules//redisbloom.so
1:M 31 Oct 2025 02:53:59.761 * <search> Redis version found by RedisSearch : 8.2.2 - oss
1:M 31 Oct 2025 02:53:59.761 * <search> RediSearch version 8.2.5 (Git=222ad3b)
1:M 31 Oct 2025 02:53:59.761 * <search> Low level api version 1 initialized successfully
1:M 31 Oct 2025 02:53:59.761 * <search> gc: ON, prefix min length: 2, min word length to stem: 4, prefix max expansions: 200, query timeout (ms): 500, timeout policy: return, cursor read size: 1000, cursor max idle (ms): 300000, max doctable size: 1000000, max number of search results:  1000000,
1:M 31 Oct 2025 02:53:59.761 * <search> Initialized thread pools!
1:M 31 Oct 2025 02:53:59.761 * <search> Disabled workers threadpool of size 0
1:M 31 Oct 2025 02:53:59.761 * <search> Subscribe to config changes
1:M 31 Oct 2025 02:53:59.761 * <search> Enabled role change notification
1:M 31 Oct 2025 02:53:59.762 * <search> Cluster configuration: AUTO partitions, type: 0, coordinator timeout: 0ms
1:M 31 Oct 2025 02:53:59.762 * <search> Register write commands
1:M 31 Oct 2025 02:53:59.762 * Module 'search' loaded from /usr/local/lib/redis/modules//redisearch.so
1:M 31 Oct 2025 02:53:59.762 * <timeseries> RedisTimeSeries version 80200, git_sha=1439d4a439ca9c063e6ef124a510abff09a5d493
1:M 31 Oct 2025 02:53:59.762 * <timeseries> Redis version found by RedisTimeSeries : 8.2.2 - oss
1:M 31 Oct 2025 02:53:59.762 * <timeseries> Registering configuration options: [
1:M 31 Oct 2025 02:53:59.762 * <timeseries> 	{ ts-compaction-policy   :              }
1:M 31 Oct 2025 02:53:59.762 * <timeseries> 	{ ts-num-threads         :            3 }
1:M 31 Oct 2025 02:53:59.762 * <timeseries> 	{ ts-retention-policy    :            0 }
1:M 31 Oct 2025 02:53:59.762 * <timeseries> 	{ ts-duplicate-policy    :        block }
1:M 31 Oct 2025 02:53:59.762 * <timeseries> 	{ ts-chunk-size-bytes    :         4096 }
1:M 31 Oct 2025 02:53:59.762 * <timeseries> 	{ ts-encoding            :   compressed }
1:M 31 Oct 2025 02:53:59.762 * <timeseries> 	{ ts-ignore-max-time-diff:            0 }
1:M 31 Oct 2025 02:53:59.762 * <timeseries> 	{ ts-ignore-max-val-diff :     0.000000 }
1:M 31 Oct 2025 02:53:59.762 * <timeseries> ]
1:M 31 Oct 2025 02:53:59.762 * <timeseries> Detected redis oss
1:M 31 Oct 2025 02:53:59.762 * <timeseries> Enabled diskless replication
1:M 31 Oct 2025 02:53:59.762 * Module 'timeseries' loaded from /usr/local/lib/redis/modules//redistimeseries.so
1:M 31 Oct 2025 02:53:59.763 * <ReJSON> Created new data type 'ReJSON-RL'
1:M 31 Oct 2025 02:53:59.763 * <ReJSON> version: 80201 git sha: unknown branch: unknown
1:M 31 Oct 2025 02:53:59.763 * <ReJSON> Exported RedisJSON_V1 API
1:M 31 Oct 2025 02:53:59.763 * <ReJSON> Exported RedisJSON_V2 API
1:M 31 Oct 2025 02:53:59.763 * <ReJSON> Exported RedisJSON_V3 API
1:M 31 Oct 2025 02:53:59.763 * <ReJSON> Exported RedisJSON_V4 API
1:M 31 Oct 2025 02:53:59.763 * <ReJSON> Exported RedisJSON_V5 API
1:M 31 Oct 2025 02:53:59.763 * <ReJSON> Enabled diskless replication
1:M 31 Oct 2025 02:53:59.763 * <ReJSON> Initialized shared string cache, thread safe: false.
1:M 31 Oct 2025 02:53:59.763 * Module 'ReJSON' loaded from /usr/local/lib/redis/modules//rejson.so
1:M 31 Oct 2025 02:53:59.763 * <search> Acquired RedisJSON_V5 API
1:M 31 Oct 2025 02:53:59.763 # Fatal: Can't initialize Background Jobs. Error message: Operation not permitted
Starting Redis Server
1:C 31 Oct 2025 02:54:06.675 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 31 Oct 2025 02:54:06.675 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 31 Oct 2025 02:54:06.675 * Redis version=8.2.2, bits=64, commit=00000000, modified=1, pid=1, just started
1:C 31 Oct 2025 02:54:06.675 * Configuration loaded
1:M 31 Oct 2025 02:54:06.675 * monotonic clock: POSIX clock_gettime
1:M 31 Oct 2025 02:54:06.676 * Running mode=standalone, port=6379.
1:M 31 Oct 2025 02:54:06.676 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 31 Oct 2025 02:54:06.676 * <bf> RedisBloom version 8.2.3 (Git=unknown)
1:M 31 Oct 2025 02:54:06.676 * <bf> Registering configuration options: [
1:M 31 Oct 2025 02:54:06.676 * <bf> 	{ bf-error-rate       :      0.01 }
1:M 31 Oct 2025 02:54:06.676 * <bf> 	{ bf-initial-size     :       100 }
1:M 31 Oct 2025 02:54:06.676 * <bf> 	{ bf-expansion-factor :         2 }
1:M 31 Oct 2025 02:54:06.676 * <bf> 	{ cf-bucket-size      :         2 }
1:M 31 Oct 2025 02:54:06.676 * <bf> 	{ cf-initial-size     :      1024 }
1:M 31 Oct 2025 02:54:06.676 * <bf> 	{ cf-max-iterations   :        20 }
1:M 31 Oct 2025 02:54:06.676 * <bf> 	{ cf-expansion-factor :         1 }
1:M 31 Oct 2025 02:54:06.676 * <bf> 	{ cf-max-expansions   :        32 }
1:M 31 Oct 2025 02:54:06.676 * <bf> ]
1:M 31 Oct 2025 02:54:06.676 * Module 'bf' loaded from /usr/local/lib/redis/modules//redisbloom.so
1:M 31 Oct 2025 02:54:06.678 * <search> Redis version found by RedisSearch : 8.2.2 - oss
1:M 31 Oct 2025 02:54:06.678 * <search> RediSearch version 8.2.5 (Git=222ad3b)
1:M 31 Oct 2025 02:54:06.679 * <search> Low level api version 1 initialized successfully
1:M 31 Oct 2025 02:54:06.679 * <search> gc: ON, prefix min length: 2, min word length to stem: 4, prefix max expansions: 200, query timeout (ms): 500, timeout policy: return, cursor read size: 1000, cursor max idle (ms): 300000, max doctable size: 1000000, max number of search results:  1000000,
1:M 31 Oct 2025 02:54:06.679 * <search> Initialized thread pools!
1:M 31 Oct 2025 02:54:06.679 * <search> Disabled workers threadpool of size 0
1:M 31 Oct 2025 02:54:06.679 * <search> Subscribe to config changes
1:M 31 Oct 2025 02:54:06.679 * <search> Enabled role change notification
1:M 31 Oct 2025 02:54:06.679 * <search> Cluster configuration: AUTO partitions, type: 0, coordinator timeout: 0ms
1:M 31 Oct 2025 02:54:06.679 * <search> Register write commands
1:M 31 Oct 2025 02:54:06.679 * Module 'search' loaded from /usr/local/lib/redis/modules//redisearch.so
1:M 31 Oct 2025 02:54:06.679 * <timeseries> RedisTimeSeries version 80200, git_sha=1439d4a439ca9c063e6ef124a510abff09a5d493
1:M 31 Oct 2025 02:54:06.679 * <timeseries> Redis version found by RedisTimeSeries : 8.2.2 - oss
1:M 31 Oct 2025 02:54:06.679 * <timeseries> Registering configuration options: [
1:M 31 Oct 2025 02:54:06.679 * <timeseries> 	{ ts-compaction-policy   :              }
1:M 31 Oct 2025 02:54:06.679 * <timeseries> 	{ ts-num-threads         :            3 }
1:M 31 Oct 2025 02:54:06.679 * <timeseries> 	{ ts-retention-policy    :            0 }
1:M 31 Oct 2025 02:54:06.679 * <timeseries> 	{ ts-duplicate-policy    :        block }
1:M 31 Oct 2025 02:54:06.679 * <timeseries> 	{ ts-chunk-size-bytes    :         4096 }
1:M 31 Oct 2025 02:54:06.679 * <timeseries> 	{ ts-encoding            :   compressed }
1:M 31 Oct 2025 02:54:06.679 * <timeseries> 	{ ts-ignore-max-time-diff:            0 }
1:M 31 Oct 2025 02:54:06.679 * <timeseries> 	{ ts-ignore-max-val-diff :     0.000000 }
1:M 31 Oct 2025 02:54:06.679 * <timeseries> ]
1:M 31 Oct 2025 02:54:06.680 * <timeseries> Detected redis oss
1:M 31 Oct 2025 02:54:06.680 * <timeseries> Enabled diskless replication
1:M 31 Oct 2025 02:54:06.680 * Module 'timeseries' loaded from /usr/local/lib/redis/modules//redistimeseries.so
1:M 31 Oct 2025 02:54:06.680 * <ReJSON> Created new data type 'ReJSON-RL'
1:M 31 Oct 2025 02:54:06.680 * <ReJSON> version: 80201 git sha: unknown branch: unknown
1:M 31 Oct 2025 02:54:06.680 * <ReJSON> Exported RedisJSON_V1 API
1:M 31 Oct 2025 02:54:06.680 * <ReJSON> Exported RedisJSON_V2 API
1:M 31 Oct 2025 02:54:06.680 * <ReJSON> Exported RedisJSON_V3 API
1:M 31 Oct 2025 02:54:06.680 * <ReJSON> Exported RedisJSON_V4 API
1:M 31 Oct 2025 02:54:06.680 * <ReJSON> Exported RedisJSON_V5 API
1:M 31 Oct 2025 02:54:06.680 * <ReJSON> Enabled diskless replication
1:M 31 Oct 2025 02:54:06.680 * <ReJSON> Initialized shared string cache, thread safe: false.
1:M 31 Oct 2025 02:54:06.680 * Module 'ReJSON' loaded from /usr/local/lib/redis/modules//rejson.so
1:M 31 Oct 2025 02:54:06.680 * <search> Acquired RedisJSON_V5 API
1:M 31 Oct 2025 02:54:06.680 # Fatal: Can't initialize Background Jobs. Error message: Operation not permitted

redis启动失败了

问题在这行,其实已经说得很直白了:

# Fatal: Can't initialize Background Jobs. Error message: Operation not permitted

意思是:Redis 启动到加载这些 Stack 模块(RedisSearch、RedisBloom、RedisTimeSeries、RedisJSON)的时候,要创建它自己的后台任务线程(background jobs / thread pool),但是系统回了一个 Operation not permitted,也就是“这事儿你不许干”。于是它直接把整个 Redis 进程给干掉了,所以你看到它一直在重复启动 → 加载模块 → 报 fatal → 又被拉起来 → 又报 fatal。

结合你的日志里这几个明显的特征,可以还原出大概的场景:
1. pid=1、重复启动,像是在 容器 / sandbox / systemd 的受限环境里跑。
2. 你用的不是“纯”redis,是带一堆模块的 Redis Stack:redisbloom.so、redisearch.so、redistimeseries.so、rejson.so 都被加载了。
3. 报错刚好出在 RedisSearch 拿到 RedisJSON_V5 API 之后:

* <search> Acquired RedisJSON_V5 API
# Fatal: Can't initialize Background Jobs. Error message: Operation not permitted

也就是说模块本身能加载,但一到创建后台线程 / 后台任务池这一步就被系统拦住了。

这在麒麟 V10 / 国产化环境里其实挺常见的:内核/容器的安全策略比较严,一些 “改调度、绑 CPU、提优先级、创建特定线程属性” 这样的系统调用会被默认的 seccomp / LSM / 容器安全策略挡掉,模块就以为“我不能正常跑后台任务”,于是直接 Fatal。

下面给你几条能落地的修法,你挑一个最适合你当前部署方式的。

方案 1:容器里放开 seccomp / capability(最简单直球)

如果你是 docker / containerd 起的 redis(从日志看很像),那 99% 是 默认 seccomp 太严,RedisSearch 在启动后台线程时做了一个被禁止的 syscall(常见是 sched_setaffinity、sched_setscheduler、setpriority 这一类),所以报了 “Operation not permitted”。

直接换成“放开安全策略”的启动方式就行了:

docker run -d \
  --name redis-stack \
  --privileged \
  --security-opt seccomp=unconfined \
  -p 6379:6379 \
  redis/redis-stack:latest

或者稍微保守一点,只加能力:

docker run -d \
  --name redis-stack \
  --cap-add SYS_NICE \
  --cap-add IPC_LOCK \
  --security-opt seccomp=unconfined \
  -p 6379:6379 \
  redis/redis-stack:latest

解释一下:
• --security-opt seccomp=unconfined:不使用默认的 seccomp 规则,很多“改进程属性”的 syscall 就不会被挡。
• --cap-add SYS_NICE:允许容器里改线程/进程优先级,很多后台 job 初始化都要这个。
• --privileged 是最粗暴的,先确认能跑起来,再慢慢收缩权限。

👉 你可以先用这个方式起一次,如果这样能正常启动,就说明问题确实是被安全策略拦住了。

方案 2:暂时别加载那些模块,先让 Redis 跑起来

你现在的 redis.conf 里肯定有类似下面几行(或者是你这个镜像 ENTRYPOINT 写死的):

loadmodule /usr/local/lib/redis/modules/redisbloom.so
loadmodule /usr/local/lib/redis/modules/redisearch.so
loadmodule /usr/local/lib/redis/modules/redistimeseries.so
loadmodule /usr/local/lib/redis/modules/rejson.so

这些就是 Redis Stack 的 4 大模块。真正报 fatal 的是这几个里的 search + json 这一段,所以你可以先注释掉所有 loadmodule,确认纯 redis 能不能在麒麟 V10 上跑:

# loadmodule ...
# loadmodule ...
# loadmodule ...
# loadmodule ...

然后重新起:

redis-server /path/to/redis.conf
•	如果纯 redis 能跑,说明 问题只在模块上;
•	那你就有两条路:
1.	要模块 → 必须放开安全策略(回到方案 1);
2.	不放开策略 → 就只能不用这些模块/只用一部分(比如只要 Bloom,不要 Search)。

方案 3:用官方 Redis,不用 Redis Stack

你现在的日志是 Redis version found by RedisSearch : 8.2.2 - oss,这是 Stack 镜像常见的写法。
如果你只是想要一个能跑的 redis 给服务用,其实装官方的 redis-7.x/8.x(不带模块)就不会去开后台 job,也就不会触发这一层的安全限制。

麒麟 V10 上一般可以直接:

# 如果你是物理机/虚机上装的
systemctl stop redis
# 自己编译官方的 redis
make MALLOC=jemalloc
# 用自己的 redis.conf 起
./src/redis-server redis.conf

或者用你们内网源里的 redis rpm,别用带一堆 module 的那个包。

方案 4:改容器的 seccomp / pod 的安全策略(k8s 场景)

如果你是 k8s 起的 redis-stack,Pod 里是默认的安全策略,也会报这个错。可以在 Pod 里加:

securityContext:
  privileged: true
  # 或者
  seccompProfile:
    type: Unconfined
  capabilities:
    add:
      - SYS_NICE
      - IPC_LOCK

改完再起,就能过 “Operation not permitted”。

你日志里的另外两个 WARNING 也顺手说一下

这两个不是致命的,但一并修了最好。

  1. 内存 overcommit

日志里反复说:

Memory overcommit must be enabled! ... add 'vm.overcommit_memory = 1' to /etc/sysctl.conf

按它说的来:

echo "vm.overcommit_memory = 1" >> /etc/sysctl.conf
sysctl -p
# 临时生效也行
sysctl -w vm.overcommit_memory=1

注意:如果你是在容器里,这条通常要在宿主机上配。

  1. somaxconn 太小
The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to 128

也是一个 sysctl:

echo "net.core.somaxconn = 1024" >> /etc/sysctl.conf
sysctl -p

总结一口气版
• 真正让它“启动失败不断重启”的根因是:Redis Stack 的模块要起后台线程,但当前运行环境(麒麟 V10 + 容器/安全策略)不允许这个 syscall → 模块直接 fatal → redis 退出。
• 最快的验证办法:用 --security-opt seccomp=unconfined 或 --privileged 起一次 redis-stack,看能不能跑。
• 如果必须在这个受限环境跑,就先去掉那些 loadmodule,让裸 redis 先跑起来。
• 顺手把 vm.overcommit_memory=1、net.core.somaxconn=1024 配一下。

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

MonkeyKing.sun

对你有帮助的话,可以打赏

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值