Closed waja closed 3 years ago
Hi @waja,
unfortunately this looks like an upstream issue (see https://github.com/nextcloud/server/issues/25742). Even with the memory limit set to -1 (no limit), it will fail (OOM Killer).
As soon as there is a fix, I will include it in this image.
hoellen
anyway ... as apc might be an issue.
# grep memcache config.php
'memcache.distributed' => '\\OC\\Memcache\\Redis',
'memcache.locking' => '\\OC\\Memcache\\Redis',
'memcache.local' => '\\OC\\Memcache\\APCu',
Running the update on a new demo instance it worked.
# grep memcache config.php
'memcache.local' => '\\OC\\Memcache\\APCu',
APCu is disabled by default on CLI which could cause issues with nextcloud’s cron jobs. Please make sure you set the apc.enable_cli to 1 on your php.ini config file or append --define apc.enable_cli=1 to the cron job call.
Thanks for the link to the docs. As it is recommended in the docs, I enabled APCu on CLI. Did you tried the update already with apc enabled?
Did you tried the update already with apc enabled?
Sorry for asking. How can I do that with the actual image?
~~The Nextcloud download servers are currently overloaded. So the last three rebuilds failed... But I just added the apcu config line manually and updated the image. So you can now use the image from Docker Hub.~~
edit: The build went through and the image is updated. So APCu for CLI should be now activated in the image.
The build went through and the image is updated. So APCu for CLI should be now activated in the image.
He @hoellen, that worked well. :party:
Many thanks!
You're welcome. Glad to hear, it worked.
Hi,
after pulling the
21.0
tag:Now the web interface is waiting for starting the update.
Many thanks, Jan.