Nextcloud version (eg, 20.0.5): 27.0.4 and 26.0.3
Operating system and version (eg, Ubuntu 20.04): debian 11
Apache or nginx version (eg, Apache 2.4.25): 2.4.56
PHP version (eg, 7.4): 8.2.8
The issue you are facing:
I did (a little bit too fast) a server update, there was a bunch of PHP updates (for 7.4, 8.1 and 8.2) and at the end, an update for Redis. After that suddenly 2 Nextcloud instances on that server stopped to work with a NC error (I have the Nextcloud background with a central box stating my IP and an error ID that changes each time I reload the page, it’s not a server error white on black).
After looking at error logs, trying to research the problem I finally did remember about that redis update, I removed my redis config from config.php and it started to work right away …
Is this the first time you’ve seen this error? (Y/N):
Yes, server has been running with redis for the last year at lesat !
The output of your config.php file in /path/to/nextcloud
(make sure you remove any identifiable information!):
'memcache.locking' => '\\OC\\Memcache\\Redis',
'memcache.local' => '\\OC\\Memcache\\Redis',
'redis' =>
array (
'host' => 'localhost',
'port' => 6379,
'timeout' => 1.5,
'password' => 'xxxxxxxxxxxx',
'dbindex' => 0,
),
I see the error on both a 27.0.4 and a 26.0.3 (PHP8.2 and PHP7.4) and it is definitely that redis upgrade that breaks. Redis was updated from 7.0.12.
I also tried migrating to a sock setup, same problem.
I ran through the changes that could affect my redis config and couldn’t find any, needless to say my Redis/NC config is pretty simple and has been working for a year …
Did anybody ran into the same problem ? Redis site says that 7.2 is like one day old, I’m surprised it went into the Debian repo so fast …
Thanks.
Pierre.