我的 redis-sentinel（版本 6）服务无法在从机上启动 - 我在这里看到了一些线程并相应地调整了服务，但仍然没有运气。我在 ubuntu 1 上。
redis.conf（启动 redis ok - 同步工作）
port 6379
protected-mode no
tcp-backlog 511
timeout 60000
tcp-keepalive 300
daemonize yes
supervised systemd
pidfile /var/run/redis/redis-server.pid
loglevel notice
logfile /var/log/redis/redis-server.log
databases 32
always-show-logo no
save ""
min-slaves-to-write 1
stop-writes-on-bgsave-error no
rdbcompression yes
rdbchecksum yes
dbfilename dump-6379.rdb
dir /var/lib/redis
slave-serve-stale-data no
slave-read-only yes
repl-diskless-sync yes
repl-diskless-sync-delay 5
repl-disable-tcp-nodelay no
slave-priority 100
lazyfree-lazy-eviction no
lazyfree-lazy-expire no
lazyfree-lazy-server-del no
slave-lazy-flush no
appendonly no
appendfilename "appendonly.aof"
appendfsync everysec
no-appendfsync-on-rewrite no
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
aof-load-truncated yes
aof-use-rdb-preamble no
lua-time-limit 5000
slowlog-log-slower-than 10000
slowlog-max-len 128
latency-monitor-threshold 0
notify-keyspace-events ""
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
list-max-ziplist-size -2
list-compress-depth 0
set-max-intset-entries 512
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
hll-sparse-max-bytes 3000
activerehashing yes
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit slave 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
hz 10
aof-rewrite-incremental-fsync yes
slaveof 10.89.8.195 6379
Sentinel conf（服务因 redis-sentinel.service: Failed with result 'protocol' 失败）
daemonize yes
protected-mode no
pidfile "/var/run/sentinel/redis-sentinel.pid"
logfile "/var/log/redis/redis-sentinel.log"
port 46379
dir "/var/lib/redis"
sentinel monitor redis4-dbregistry1d 10.89.8.195 6379 2
sentinel down-after-milliseconds redis4-dbregistry1d 10000
sentinel failover-timeout redis4-dbregistry1d 30000
# Generated by CONFIG REWRITE
user default on nopass sanitize-payload ~* &* +@all
sentinel myid 46d9c29a839b7b671e2ad39bc6519e4c58f824f2
sentinel config-epoch redis4-dbregistry1d 0
sentinel leader-epoch redis4-dbregistry1d 0
sentinel current-epoch 0
sentinel known-replica redis4-dbregistry1d 10.89.8.240 6379
sentinel known-replica redis4-dbregistry1d 10.89.8.224 6379
sentinel known-sentinel redis4-dbregistry1d 10.89.8.195 46379 adf4a11563eb0e99e2ca06bb495ff2d666261bce
哨兵日志中的错误 - 哨兵正在关闭（'用户请求关闭...'）
5213:X 17 May 2021 07:20:26.334 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
5218:X 17 May 2021 07:20:26.836 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
5222:X 17 May 2021 07:20:27.340 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
5241:X 17 May 2021 07:20:27.819 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
5241:X 17 May 2021 07:20:27.819 # Redis version=6.2.3, bits=64, commit=00000000, modified=0, pid=5241, just started
5241:X 17 May 2021 07:20:27.819 # Configuration loaded
5241:signal-handler (1621236027) Received SIGTERM scheduling shutdown...
5241:X 17 May 2021 07:20:27.820 * monotonic clock: POSIX clock_gettime
5241:X 17 May 2021 07:20:27.821 * Running mode=sentinel, port=46379.
5241:X 17 May 2021 07:20:27.821 # Sentinel ID is 46d9c29a839b7b671e2ad39bc6519e4c58f824f2
5241:X 17 May 2021 07:20:27.821 # +monitor master redis4-dbregistry1d 10.89.8.195 6379 quorum 2
5241:X 17 May 2021 07:20:27.822 # User requested shutdown...
5241:X 17 May 2021 07:20:27.822 * Removing the pid file.
5241:X 17 May 2021 07:20:27.822 # Sentinel is now ready to exit, bye bye...
Atm 所有节点上的所有哨兵都已关闭 - 主哨兵是否需要先启动并运行，然后其他哨兵才能运行..？
答案 0 :(得分：0)
当我使用您的 conf 文件运行 redis 时，它运行良好。 conf文件好像没有问题。
你见过这个帖子吗？我认为这会有所帮助。
Determining why Redis is receiving a SIGTERM every minute or two