在Debian上使用.dpkg包将redis-server和redis-sentinel从版本3.0.7更新到3.2.7之后,我在引导系统时得到以下错误:
фев 17 20:50:21 vm systemd[431]: Failed at step RUNTIME_DIRECTORY spawning /bin/run-parts: File exists
фев 17 20:50:21 vm systemd[1]: Starting OpenBSD Secure Shell server...
фев 17 20:50:21 vm systemd[432]: Failed at step RUNTIME_DIRECTORY spawning /bin/run-parts: File exists
фев 17 20:50:21 vm systemd[450]: Failed at step RUNTIME_DIRECTORY spawning /usr/bin/redis-sentinel: File exists
фев 17 20:50:21 vm systemd[1]: Started /etc/rc.local Compatibility.
фев 17 20:50:21 vm systemd[1]: redis-sentinel.service: control process exited, code=exited status=233
фев 17 20:50:21 vm systemd[452]: Failed at step RUNTIME_DIRECTORY spawning /usr/bin/redis-server: File exists
фев 17 20:50:21 vm systemd[1]: Failed to start Advanced key-value store.
фев 17 20:50:21 vm systemd[1]: Unit redis-sentinel.service entered failed state.
фев 17 20:50:21 vm systemd[1]: redis-server.service: control process exited, code=exited status=233
фев 17 20:50:21 vm systemd[1]: Failed to start Advanced key-value store.
фев 17 20:50:21 vm systemd[1]: Unit redis-server.service entered failed state.我该如何解决这个问题?
发布于 2017-05-19 01:35:00
这是由redis包中的更改引起的,其中它现在具有一个将创建redis目录的RuntimeDirectoryMode。(参见git提交https://github.com/lamby/pkg-redis/commit/1cecea5abcb2ce05beacd4347977634d06c59cef)
因此,解决方案是停止redis服务,删除现有的/var/run/redis目录,然后重新启动服务。
发布于 2018-05-21 17:16:44
我的问题是,无论出于什么原因,sentinel的日志文件都属于root。
我在/var/log/messages中看到了错误:
redis-sentinel: *** FATAL CONFIG FILE ERROR ***
redis-sentinel: Reading the configuration file, at line 139
redis-sentinel: >>> 'logfile "/var/log/redis/sentinel.log"'
redis-sentinel: Can't open the log file: Permission denied一旦我将权限更改为redis,我就可以启动redis-sentinel了
https://stackoverflow.com/questions/42313007
复制相似问题