Ubuntu 无法启动高级键值存储。redis-server.service:控制进程已退出,代码=退出状态=1
redis服务器在我有nginx、apache、php和mysql的服务器上无法工作 是否有可能导致以下问题的软件包 PS:安装BBB时出现此错误 redis-server.service:控制进程已退出,代码=退出状态=1 无法启动高级键值存储Ubuntu 无法启动高级键值存储。redis-server.service:控制进程已退出,代码=退出状态=1,ubuntu,redis,bigbluebutton,Ubuntu,Redis,Bigbluebutton,redis服务器在我有nginx、apache、php和mysql的服务器上无法工作 是否有可能导致以下问题的软件包 PS:安装BBB时出现此错误 redis-server.service:控制进程已退出,代码=退出状态=1 无法启动高级键值存储 -- -- The result is failed. Apr 05 12:28:44 ns3081715 systemd[1]: redis-server.service: Unit entered failed state. Apr 05 12
--
-- The result is failed.
Apr 05 12:28:44 ns3081715 systemd[1]: redis-server.service: Unit entered failed state.
Apr 05 12:28:44 ns3081715 systemd[1]: redis-server.service: Failed with result 'exit-code'.
Apr 05 12:28:44 ns3081715 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Apr 05 12:28:44 ns3081715 systemd[1]: Stopped Advanced key-value store.
-- Subject: Unit redis-server.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit redis-server.service has finished shutting down.
Apr 05 12:28:44 ns3081715 systemd[1]: Starting Advanced key-value store...
-- Subject: Unit redis-server.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit redis-server.service has begun starting up.
Apr 05 12:28:44 ns3081715 run-parts[19223]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Apr 05 12:28:44 ns3081715 redis-server[19239]: *** FATAL CONFIG FILE ERROR ***
Apr 05 12:28:44 ns3081715 redis-server[19239]: Reading the configuration file, at line 108
Apr 05 12:28:44 ns3081715 redis-server[19239]: >>> 'logfile /var/log/redis/redis-server.log'
Apr 05 12:28:44 ns3081715 redis-server[19239]: Can't open the log file: Permission denied
Apr 05 12:28:45 ns3081715 systemd[1]: redis-server.service: Control process exited, code=exited status=1
Apr 05 12:28:45 ns3081715 systemd[1]: Failed to start Advanced key-value store.
-- Subject: Unit redis-server.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit redis-server.service has failed.
--
-- The result is failed.
Apr 05 12:28:45 ns3081715 systemd[1]: redis-server.service: Unit entered failed state.
Apr 05 12:28:45 ns3081715 systemd[1]: redis-server.service: Failed with result 'exit-code'.
Apr 05 12:28:45 ns3081715 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Apr 05 12:28:45 ns3081715 systemd[1]: Stopped Advanced key-value store.
-- Subject: Unit redis-server.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit redis-server.service has finished shutting down.
Apr 05 12:28:45 ns3081715 systemd[1]: Starting Advanced key-value store...
-- Subject: Unit redis-server.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit redis-server.service has begun starting up.
Apr 05 12:28:45 ns3081715 run-parts[19251]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Apr 05 12:28:45 ns3081715 redis-server[19270]: *** FATAL CONFIG FILE ERROR ***
Apr 05 12:28:45 ns3081715 redis-server[19270]: Reading the configuration file, at line 108
Apr 05 12:28:45 ns3081715 redis-server[19270]: >>> 'logfile /var/log/redis/redis-server.log'
Apr 05 12:28:45 ns3081715 redis-server[19270]: Can't open the log file: Permission denied
Apr 05 12:28:45 ns3081715 systemd[1]: redis-server.service: Control process exited, code=exited status=1
Apr 05 12:28:45 ns3081715 systemd[1]: Failed to start Advanced key-value store.
-- Subject: Unit redis-server.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit redis-server.service has failed.
--
-- The result is failed.
Apr 05 12:28:45 ns3081715 systemd[1]: redis-server.service: Unit entered failed state.
Apr 05 12:28:45 ns3081715 systemd[1]: redis-server.service: Failed with result 'exit-code'.
其他日志
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit redis-server.service has failed.
> --
> -- The result is failed. Apr 05 12:38:23 ns3081715 systemd[1]: redis-server.service: Unit entered failed state. Apr 05 12:38:23
> ns3081715 systemd[1]: redis-server.service: Failed with result
> 'exit-code'. Apr 05 12:38:23 ns3081715 systemd[1]:
> redis-server.service: Service hold-off time over, scheduling restart.
> Apr 05 12:38:23 ns3081715 systemd[1]: Stopped Advanced key-value
> store.
> -- Subject: Unit redis-server.service has finished shutting down
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit redis-server.service has finished shutting down. Apr 05 12:38:23 ns3081715 systemd[1]: Starting Advanced key-value store...
> -- Subject: Unit redis-server.service has begun start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit redis-server.service has begun starting up. Apr 05 12:38:23 ns3081715 run-parts[20653]: run-parts: executing
> /etc/redis/redis-server.pre-up.d/00_example Apr 05 12:38:23 ns3081715
> redis-server[20669]: *** FATAL CONFIG FILE ERROR *** Apr 05 12:38:23
> ns3081715 redis-server[20669]: Reading the configuration file, at line
> 108 Apr 05 12:38:23 ns3081715 redis-server[20669]: >>> 'logfile
> /var/log/redis/redis-server.log' Apr 05 12:38:23 ns3081715
> redis-server[20669]: Can't open the log file: Permission denied Apr 05
> 12:38:23 ns3081715 systemd[1]: redis-server.service: Control process
> exited, code=exited status=1 Apr 05 12:38:23 ns3081715 systemd[1]:
> Failed to start Advanced key-value store.
> -- Subject: Unit redis-server.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit redis-server.service has failed.
> --
> -- The result is failed. Apr 05 12:38:23 ns3081715 systemd[1]: redis-server.service: Unit entered failed state. Apr 05 12:38:23
> ns3081715 systemd[1]: redis-server.service: Failed with result
> 'exit-code'. Apr 05 12:38:23 ns3081715 systemd[1]:
> redis-server.service: Service hold-off time over, scheduling restart.
> Apr 05 12:38:23 ns3081715 systemd[1]: Stopped Advanced key-value
> store.
> -- Subject: Unit redis-server.service has finished shutting down
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit redis-server.service has finished shutting down. Apr 05 12:38:23 ns3081715 systemd[1]: redis-server.service: Start request
> repeated too quickly. Apr 05 12:38:23 ns3081715 systemd[1]: Failed to
> start Advanced key-value store.
> -- Subject: Unit redis-server.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit redis-server.service has failed.
> --
> -- The result is failed. Apr 05 12:38:24 ns3081715 sshd[20498]: Failed password for root from 218.65.30.46 port 47702 ssh2 Apr 05 12:38:24
> ns3081715 sshd[20498]: Received disconnect from 218.65.30.46 port
> 47702:11: [preauth] Apr 05 12:38:24 ns3081715 sshd[20498]:
> Disconnected from 218.65.30.46 port 47702 [preauth] Apr 05 12:38:24
> ns3081715 sshd[20498]: PAM 2 more authentication failures; logname=
> uid=0 euid=0 tty=ssh ruser= rhost=218.65.30.46 user=root Apr 05
> 12:38:24 ns3081715 sshd[20540]: Failed password for root from
> 217.61.5.246 port 42706 ssh2 Apr 05 12:38:24 ns3081715 sshd[20540]: Received disconnect from 217.61.5.246 port 42706:11: disconnected by
> user [preauth] Apr 05 12:38:24 ns3081715 sshd[20540]: Disconnected
> from 217.61.5.246 port 42706 [preauth] Apr 05 12:38:24 ns3081715
> sshd[20540]: PAM 1 more authentication failure; logname= uid=0 euid=0
> tty=ssh ruser= rhost=217.61.5.246 user=root Apr 05 12:38:25 ns3081715
> sshd[20680]: pam_unix(sshd:auth): authentication failure; logname=
> uid=0 euid=0 tty=ssh ruser= rhost=218.65.30.46 user=root
我在ubuntu 16.04上也遇到过同样的问题。这是在更新redis服务器包之后发生的 服务无法启动,但使用手动方式运行服务器
/usr/bin/redis-server /etc/redis/redis.conf
让我们开始吧
/var/log/redis/redis.log不会提供关于它的有用信息
我所做的是(在ubutu 16.04上)删除redis服务器及其所有配置文件
在/etc/redis中有一个遗留文件dumb.rdb,因此可以确定:
sudo rm -rf /etc/redis/dump.rdb
然后重新安装redis服务器
sudo apt-get update
sudo apt-get install redis-server
这就为我解决了问题
记住,虽然这只是我的系统。显然,redis服务器无法启动错误可能是由于不同系统上的许多情况造成的,例如:
编辑:更正了一个输入错误我刚刚在debian 10.1软件包存储库中新安装了redis 5.0.3时遇到了同样的问题 对我来说,解决方案是让用户redis访问配置文件(read)和日志文件(read-write)
chown -R redis:redis /var/log/redis
chmod -R u+rwX,g+rwX,u+rx /var/log/redis
chmod +r /etc/redis/redis.conf
对redis.conf的更改
对redis.conf文件进行以下更改以重新启动redis服务器。通过执行以下命令编辑redis.conf文件
nano/etc/redis/redis.conf
将行绑定127.0.0.1::1更改为127.0.0.1
将行监督编号更改为spervised systemd
保存更改并关闭文件。下一步是启动Redis服务器。执行以下命令启动Redis服务器并为Redis服务创建必要的符号链接
systemctl启用redis服务器
systemctl后台程序重新加载
现在您已经全部设置好了,您可以通过执行命令systemctl status redis来检查服务的状态来验证它。在
/etc/redis/redis.conf
中更改默认路径和文件位置时会遇到一个陷阱。我花了一个晚上才发现,系统服务的读写权限不仅取决于文件系统权限,还取决于在服务本身的单位文件中授予的权限:
如果需要将日志文件和数据库重新定位到默认位置之外的某个位置,则需要根据需要调整/lib/systemd/system/redis server.service
中的ReadWriteDirectories
指令
不要忘记运行systemctl守护进程重新加载
,您应该可以systemctl启动redis服务器
如果单位文件被替换,软件包更新可能会破坏修复程序。对于我来说,解决方案是:
sudo ps aux | grep redis
然后我杀死了redis服务器
PID:
sudo kill 7453
最后:
sudo service redis start
你能为你的服务做一个日志并重新启动服务吗。。?使用systemctl重新启动您的.services时会出现输入错误
sudo-rf/etc/redis/dump.rdb
应该是rm-rf
,在不更改任何配置文件的情况下工作。谢谢它也解决了我的问题。手动运行redis服务器给了我我要查找的错误。当日志没有显示任何有用的信息时,错误输出向我显示了错误。谢谢你的启发。回答正确,可能会解决一些人的问题,但在我的例子中,我执行了上述命令,但仍然得到:“未能启用单元:单元文件系统ctl.service不存在”我在目录所有权方面遇到了类似的问题,它适用于根目录/
。我用chown root.root/
解决了这个问题。我每次sudo rm-fr/var/log/*
都会遇到这个问题……在我的例子中,redis dir被删除了。我使用以下命令:sudomkdir-p/var/log/redis/&&sudotouch/var/log/redis/redis-server.log&&sudochown-redis:redis/var/log/redis/redis-server.log
对我来说,这个答案帮助我解决了问题。原来有两个redis服务器进程已经在运行。不得不杀了那两个然后重新开始服务。
sudo service redis start