【Redis】centos7 systemctl 启动 Redis 失败

原创已于 2022-05-24 22:55:56 修改 · 1.3w 阅读

8 ·

本内容遵循CC 4.0 BY-SA版权协议

标签

#redis

于 2021-03-16 01:27:10 首次发布

数据开发专栏收录该内容

42 篇文章

订阅专栏

本文记录了一次Redis服务启动失败的排查过程。故障表现为启动长时间阻塞并最终失败。通过检查systemd服务文件，发现将Type=forking注释掉可以解决问题。此问题源于Redis配置为不以守护进程方式运行，而systemd期望其行为为传统UNIX守护进程。

今天启动 Redis 时阻塞很长时间，之后显示启动失败，启动状态如下。

systemd[1]: redis.service start operation timed out. Terminating.
systemd[1]: Failed to start A persistent key-value database.
systemd[1]: Unit redis.service entered failed state.

看了下 service 文件，发现 Systemd 启动命令如下

ExecStart=/usr/sbin/redis-server /etc/redis.conf

手动运行这条命令，发现是正常的，所以猜想是 service 文件的问题，后来发现只需要把 [Service] 部分的 Type=forking 注释掉就行了。

[Service]
# Type=forking
# PIDFile=/var/run/redis/redis.pid
ExecStart=/usr/sbin/redis-server /etc/redis.conf
User=redis
Group=redis

之后重新加载 Service 文件并启动 Redis 服务

sudo systemctl daemon-reload

sudo systemctl start redis

Man pages 对 Systemd 服务启动类型 Type 的解释如下

If set to forking, it is expected that the process configured with ExecStart= will call fork() as part of its start-up. The parent process is expected to exit when start-up is complete and all communication channels are set up. The child continues to run as the main daemon process. This is the behavior of traditional UNIX daemons. If this setting is used, it is recommended to also use the PIDFile= option, so that systemd can identify the main process of the daemon. systemd will proceed with starting follow-up units as soon as the parent process exits.

因为 Redis 配置文件里配置的是
daemonize no