long running and working nextcloud recently autoupdated via watchtower
since then, i have a white screen and nothing else.
occ update:check shows
occ update:check
An unhandled exception has been thrown:
Exception: Redis cluster config is missing the āseedsā attribute in /nextcloud/lib/private/RedisFactory.php:86
Stack trace: #0 /nextcloud/lib/private/RedisFactory.php(164): OC\RedisFactory->create() #1 /nextcloud/lib/private/Memcache/Redis.php(43): OC\RedisFactory->getInstance() #2 /nextcloud/lib/private/Memcache/Factory.php(115): OC\Memcache\Redis->__construct(āfe784447876118aā¦ā) #3 /nextcloud/lib/private/Server.php(1051): OC\Memcache\Factory->createLocking(ālockā) #4 /nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(160): OC\Server->OC{closure}(Object(OC\Server)) #5 /nextcloud/3rdparty/pimple/pimple/src/Pimple/Container.php(118): OC\AppFramework\Utility\SimpleContainer->OC\AppFramework\Utility{closure}(Object(Pimple\Container)) #6 /nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(127): Pimple\Container->offsetGet(āOCP\Lock\ILockiā¦ā) #7 /nextcloud/lib/private/ServerContainer.php(136): OC\AppFramework\Utility\SimpleContainer->query(āOCP\Lock\ILockiā¦ā, fal
as i havenāt a redis cluster configured and nothing in the config.php iām a little screwed hereā¦
neither google nor forum search revealed something.
Is redis cluster mode now mandatory with ver 22?
Just started having the same error. I had to disable redis from config.php for it to stop working. (My whole installation was Erroring 500). It then prompted me with update 22.1.0. I did the update and all is working!
I am going to check to see if I can enable it again.
I faced the same issue, disable redis config didnāt works for me
Iām using docker image so I canāt change RedisFactory.php manually (previous docker image must be removed to upgrade)
UPDATE - Mine was related to an improper S3/DigitalOcean Spaces implementation.
I was using some guidance Iād found elsewhere, and the code block for mounting the space was incorrect. I updated to the information in the Nextcloud Admin Guide, and viola.
Hello! I have some problems with temporary fix. When I try make any changes in lib/private/RedisFactory.php, I canāt do this, cause file is unwritable. Also I canāt change permissions because: āchmod: changing permissions of āRedisFactory.phpā: Read-only file systemā. Please help me to solve this problem.
Same issue here first time after update to 22.1.1 and still there after update to 22.2.0 today. The temporary fix from Shadow256 (thanks a lot!) did work for me, but how does the final solution look like?
to update from 21.0.5 to 22.2
i change RedisFactory.php
to $isCluster = false;
update work to 22.2
now
Technical information
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
As stated before Iām running the nextcloud snap on ubuntu 20.04.3 LTS and since nextcloud 22.2.0snap2 iām not observing the failure anymore and I do not have to apply any of the above workarounds (Neither code change related to $isCluster = ... nor the redis changes in config.php). None of them seems to be to be permanently applied in the new release either. So it must have been some other change, that is fixing the situation for me. I can see that various redis binaries in ./bin/redis-* have changed - no idea wtether that fixed things.
I have a second snap instance in my LAN that has not suffered from the problem at all, not even with version 22.0 or 22.1.
Can confirm that the bug still exists in 22.2.3. I updated yesterday and once again the update process crashed in the middle (to be precise the moment the RedisFactory.php got overwritten with the default file from the installation package).
I had to apply the Shadow256 (KUDOS for your work!!! ) during the update, refresh the update and it went to the end. Now I have the same integrity check error again as posted by MikeZuluUSA here.
My setup (note: no docker image - standard server installation):
Ubuntu 20.04 LTS
MariaDB
Apache
PHP 7.4
As asked before by someone else: Is there a bug report in place or does the issue already have some dev-attention? I can more ore less just C&P what is already in this thread because I have the exact same error-situation, so Iād like to be more redundant than just confirming the issue (for I am not that experienced in posting professional bug reports).