Thanks for the quick response.That's weird. I got this error right after (during, in fact) the install, before I could have made any configuration errors, so I didn't expect this to be unreproducible.
This is the full output from journalctl -xe: -- Unit redis-server.service has begun starting up.Aug 17 01:52:52 illium systemd[14621]: redis-server.service: Failed at step NAMESPACE spawning /bin/run-parts: Stale file handle
-- Subject: Process /bin/run-parts could not be executed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The process /bin/run-parts could not be executed and failed. -- -- The error number returned by this process is 116.Aug 17 01:52:52 illium systemd[14686]: redis-server.service: Failed at step NAMESPACE spawning /usr/bin/redis-server: Stale file handle
-- Subject: Process /usr/bin/redis-server could not be executed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The process /usr/bin/redis-server could not be executed and failed. -- -- The error number returned by this process is 116.Aug 17 01:52:52 illium systemd[1]: redis-server.service: Control process exited, code=exited status=226
Aug 17 01:52:52 illium 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.Aug 17 01:52:52 illium systemd[1]: redis-server.service: Unit entered failed state. Aug 17 01:52:52 illium systemd[1]: redis-server.service: Failed with result 'exit-code'. Aug 17 01:52:52 illium systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Aug 17 01:52:52 illium 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.Aug 17 01:52:52 illium systemd[1]: redis-server.service: Start request repeated too quickly.
Aug 17 01:52:52 illium 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.If I manually run /usr/bin/redis-server /etc/redis/redis.conf, Redis starts up fine, which made me believe this is a problem with the init script.
When I researched the error given (code=exited status=226) I found something about /var/tmp/ being symlinked to /tmp/ which can cause the problem. I thought maybe the same thing extended to /var/run/ (which is symlinked to /run/ on my machine) but changing the line
ReadWriteDirectories=-/var/run/redis to ReadWriteDirectories=-/run/redis did not solve my problem. If you need more info let me know :) Regards, Lars
signature.asc
Description: OpenPGP digital signature
