Hello,
I am trying to run a Redis server for development purposes on my machine.
I installed the “redis” package.
When running the “redis-server” command, no issues at all. However it gets tricky when trying to use the systemd services.
I renamed the default.example.conf to default.conf, and enabled the service using:
$ systemctl enable redis@default
However, the Redis server doesn’t start when using
$ systemctl start redis@default
It gives these errors in /var/log/redis/default.log:
6520:C 06 Nov 2023 17:40:48.129 # systemd supervision error: NOTIFY_SOCKET not found!
6520:C 06 Nov 2023 17:40:48.129 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
6520:C 06 Nov 2023 17:40:48.129 * Redis version=7.2.3, bits=64, commit=00000000, modified=0, pid=6520, just started
6520:C 06 Nov 2023 17:40:48.129 * Configuration loaded
6520:M 06 Nov 2023 17:40:48.130 * Increased maximum number of open files to 10032 (it was originally set to 1024).
6520:M 06 Nov 2023 17:40:48.130 * monotonic clock: POSIX clock_gettime
6520:M 06 Nov 2023 17:40:48.130 * Running mode=standalone, port=6379.
6520:M 06 Nov 2023 17:40:48.130 * Server initialized
6520:M 06 Nov 2023 17:40:48.130 * Ready to accept connections tcp
6520:M 06 Nov 2023 17:40:48.130 # systemd supervision error: NOTIFY_SOCKET not found!
6520:M 06 Nov 2023 17:40:48.130 # systemd supervision error: NOTIFY_SOCKET not found!
6520:signal-handler (1699288889) Received SIGINT scheduling shutdown...
6520:M 06 Nov 2023 17:41:29.199 * User requested shutdown...
6520:M 06 Nov 2023 17:41:29.199 # systemd supervision error: NOTIFY_SOCKET not found!
6520:M 06 Nov 2023 17:41:29.199 * Saving the final RDB snapshot before exiting.
6520:M 06 Nov 2023 17:41:29.199 # systemd supervision error: NOTIFY_SOCKET not found!
6520:M 06 Nov 2023 17:41:29.205 * DB saved on disk
6520:M 06 Nov 2023 17:41:29.205 * Removing the pid file.
6520:M 06 Nov 2023 17:41:29.205 # Redis is now ready to exit, bye bye...
I tried several changes in Redis’ config, with the daemonize (yes / no) and I checked supervised was set on systemd.
Loading the config using the command line provided in the ExecStart section of the service works.
How can I solve this issue?
Thank you 