On 4/26/25 10:04 PM, David C Rankin wrote:
Is there something else needed to switch nextcloud from redis to valkey?
YES
1. I stopped/disabled redis.
2. Installed valkey removing redis
3. Updated all configs per both wikis
4. started/enabled valkey (all good)
5. restarted httpd (all good)
If using php-legacy-fpm, don't forget:
5(a). systemctl restart php-legacy-fpm (all good)
6. attempted to access nextcloud (failed with the error above)
Now it succeeds.
Also, when enabling unixsocket in /etc/valkey/valkey.conf you must
also set:
port 0
Now systemctl status valkey correctly shows:
CGroup: /system.slice/valkey.service
└─4176 "/usr/bin/valkey-server
unixsocket:/run/valkey/valkey.sock"
The wiki is reads as if it is optional to leave both port 6379 and
enable unixsocket. I'm sure that may read as mutually exclusive for
those that are experts in the area, but it provided a bit of confusion
for those that don't deal in tweaking caches on a regular basis.
Sorry for the noise, hope this saves someone else a bit of trouble.
--
David C. Rankin, J.D.,P.E.
