Nextcloud version (eg, 20.0.5): AIO 4.6.2
Operating system and version (eg, Ubuntu 20.04): Ubuntu 22.04
Apache or nginx version (eg, Apache 2.4.25): AIO / Docker
The issue you are facing:
After responding to updates available message I updated the master container and then the other containers via the web interface. However the containers Nextcloud and Apache don’t really start.
Apache logs: Waiting for Nextcloud to start …
Nextcloud logs:
2023-03-23 19:36:12.801905+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Configuring Redis as session handler...
Setting php max children...
Checking connection to appstore
Appstore is reachable
Maintenance mode already disabled
Getting and backing up the status of apps for later, this might take a while...
Disabling apps before the update in order to make the update procedure more safe. This can take a while...
No such app enabled: deck
No such app enabled: recognize
No such app enabled: previewgenerator
No such app enabled: fulltextsearch
No such app enabled: fulltextsearch_elasticsearch
No such app enabled: spreed
No such app enabled: contacts
No such app enabled: notify_push
No such app enabled: calendar
No such app enabled: files_fulltextsearch
No such app enabled: richdocuments
No such app enabled: notes
No such app enabled: mail
No such app enabled: collectives
No such app enabled: tasks
recognize new version available: 3.7.0
It seems to hang on an attempt to update the app Recognize. If that is the case, how can I disable the app / skip the attempt to update that app although Nextcloud itself is not starting?
Or if any other solution… I’d love to hear!
Hi, I think you simply need to wait until the app is correctly updated. How long is the update already taking?
Well over 20 minutes. Seems way too long. Would I be able to see progress of that somewhere?
Server stats show little network or processor use for example.
I guess this is an issue of the recognize app and should be discussed there: Issues · nextcloud/recognize · GitHub Since the update process should be limited by a timeout imo.
As workaround you could try to disable the recognize app with sudo docker -it --user www-data php occ app:disable recognize. But I am unsure about the outcome.
Could be an issue with the app, I had issues with it before and will not use it anymore for now.
It was already disabled but I used app:remove to remove it. Then stopped all containers and restarted. There is change at least, which is positive, it’s now hanging on Mail, but I’ll give it some time:
now
------------------------------
2023-03-23 20:19:24.83113+01
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Installing imagemagick via apk...
Enabling Imagick...
Configuring Redis as session handler...
Setting php max children...
Checking connection to appstore
Appstore is reachable
Maintenance mode already disabled
Getting and backing up the status of apps for later, this might take a while...
Disabling apps before the update in order to make the update procedure more safe. This can take a while...
No such app enabled: deck
No such app enabled: previewgenerator
No such app enabled: fulltextsearch
No such app enabled: fulltextsearch_elasticsearch
No such app enabled: spreed
No such app enabled: contacts
No such app enabled: notify_push
No such app enabled: calendar
No such app enabled: files_fulltextsearch
No such app enabled: richdocuments
No such app enabled: notes
No such app enabled: mail
No such app enabled: collectives
No such app enabled: tasks
contacts new version available: 5.2.0
contacts updated
calendar new version available: 4.3.1
calendar updated
richdocuments new version available: 7.1.2
richdocuments updated
notes new version available: 4.7.2
notes updated
mail new version available: 2.2.5
And success! Thanks a lot for thinking along. Solution that worked:
Remove the app that wouldn’t update with occ command app:remove
Kill all containers
Restart Nextcloud AIO container (in my case simply docker compose up -d)
All apps were disabled after it started succesfully and I had to manually re-enable them, though.