Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to Nextcloud 21.0 fails #47

Closed
waja opened this issue Feb 22, 2021 · 9 comments
Closed

Upgrade to Nextcloud 21.0 fails #47

waja opened this issue Feb 22, 2021 · 9 comments

Comments

@waja
Copy link

waja commented Feb 22, 2021

Hi,

after pulling the 21.0 tag:

nextcloud_1                            | Permissions in /data are correct.
nextcloud_1                            | Permissions in /config are correct.
nextcloud_1                            | Permissions in /apps2 are correct.
nextcloud_1                            | Updating permissions in /var/log...
nextcloud_1                            | Updating permissions in /php...
nextcloud_1                            | Updating permissions in /nginx...
nextcloud_1                            | Updating permissions in /tmp...
nextcloud_1                            | Updating permissions in /etc/s6.d...
nextcloud_1                            | Done updating permissions.
nextcloud_1                            | Check for UserID 1000
nextcloud_1                            | Creating user nextcloud with UID=1000 and GID=1000.
nextcloud_1                            |
nextcloud_1                            | Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php on line 133
nextcloud_1                            |
nextcloud_1                            | Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 266240 bytes) in /nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php on line 133

Now the web interface is waiting for starting the update.

    environment:
      - UID=1000
      - GID=1000
      - UPLOAD_MAX_SIZE=10G
      - APC_SHM_SIZE=128M
      - OPCACHE_MEM_SIZE=128
      - CRON_PERIOD=15m
      - TZ=Europe/Berlin

Many thanks, Jan.

@hoellen
Copy link
Owner

hoellen commented Feb 22, 2021

Hi @waja,

unfortunately this looks like an upstream issue (see nextcloud/server#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

@waja
Copy link
Author

waja commented Feb 23, 2021

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',

@waja
Copy link
Author

waja commented Feb 23, 2021

Running the update on a new demo instance it worked.

# grep memcache config.php
  'memcache.local' => '\\OC\\Memcache\\APCu',

@waja
Copy link
Author

waja commented Feb 23, 2021

https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html#id1 states:

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.

@hoellen
Copy link
Owner

hoellen commented Feb 23, 2021

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?

@waja
Copy link
Author

waja commented Feb 23, 2021

Did you tried the update already with apc enabled?

Sorry for asking. How can I do that with the actual image?

@hoellen
Copy link
Owner

hoellen commented Feb 23, 2021

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.

@waja
Copy link
Author

waja commented Feb 23, 2021

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!

@hoellen
Copy link
Owner

hoellen commented Feb 23, 2021

You're welcome. Glad to hear, it worked.

@hoellen hoellen closed this as completed Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants