Hey,
I'm currently migrating my NodeBB installation to another VPS and I came across an error when installing redis-server
. The installation of redis-server
went flawlessly, until I tried to check the status of Redis. (service redis-server status
). It printed out a miscellaneous error with no information about what could be wrong... I've tried to fix this error for hours and I still can't figure out what could be the issue.
My first idea was that perhaps Ubuntu systemd was doing something nasty, because when manually starting Redis via $ redis-server
, it started properly with no errors.
Error log when doing service redis-server status
:
● redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Sun 2016-06-26 15:11:08 CEST; 29min ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Process: 8492 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=1/FAILURE)
Process: 8487 ExecStartPre=/bin/run-parts --verbose /etc/redis/redis-server.pre-up.d (code=exited, status=0/SUCCESS)
Jun 26 15:11:08 vps291166 systemd[1]: redis-server.service: Control process exited, code=exited status=1
Jun 26 15:11:08 vps291166 systemd[1]: Failed to start Advanced key-value store.
Jun 26 15:11:08 vps291166 systemd[1]: redis-server.service: Unit entered failed state.
Jun 26 15:11:08 vps291166 systemd[1]: redis-server.service: Failed with result 'exit-code'.
Jun 26 15:11:08 vps291166 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jun 26 15:11:08 vps291166 systemd[1]: Stopped Advanced key-value store.
Jun 26 15:11:08 vps291166 systemd[1]: redis-server.service: Start request repeated too quickly.
Jun 26 15:11:08 vps291166 systemd[1]: Failed to start Advanced key-value store.
And service redis-server start
just prints this line:
Job for redis-server.service failed because the control process exited with error code. See "systemctl status redis-server.service" and "journalctl -xe" for details.