With Nextcloud 14.0.2 and now 15.0.0 my system is set to automatically execute updates.
Because of that, every couple of days it switches to maintenance mode and gets stuck there.
So every couple of days I need to log into the shell and disable it with the occ command or by editing the config.php file.
This doesnt fix the root cause though. It isnreally annoying to be honest.
So how can I fix the system in order to automatically go back to maintenance mode off or to finally stop maintenance mode forever?
But I am not sure if that is what is related to your issue. How do you do the automatically executed updates? Normally there isn’t an update every couple of days, so worst case it should only leave you in maintenance mode after a real update (once a month), that is bad enough.
I’m using NextcloudPi with nc-autoupdate and nc-autoupdate-nextcloud so that NextCloudPi and NextCloud specific updates are getting executed. So it’s probably the NextcloudPi Updates that happen more often.
Executing sudo -u www-data php updater/updater.phar results in:
Nextcloud Updater - version: v14.0.2RC2-7-g57268cb
Current version is 15.0.0
No update available.
Nothing to do.
Executing sudo -u www-data php occ upgrade results in:
Nextcloud is already latest version
HI Schmu, seems to be a dead end.
Done the whole procedure with the result of getting the version number v14.0.2RC2-7-g57268cb again. Searching the updater.phar file in the https://download.nextcloud.com/server/releases/nextcloud-15.0.0.zip file shows that this seems to be the current version of that package.
I’ve checked for the root and pi user, same result.
What I acutally do is using the nc (or ncp for NextcloudPi) commands:
I have been updating through nc-update but why isn’t Nextcloud on the latest version?
nc-update only updates NextCloudPi related stuff. In order to upgrade the Nextcloud instance itself you use nc-update-nextcloud. Or better still : enable nc-autoupdate and nc-autoupdate-nextcloud so your instance > will always be automatically update to the latest stable version of NCP and NC. It is not advisable (for NCP > users) to use NC’s own update facility at present.
Sorry… need to correct my last reply:
User www-data has the mentioned cronjob. root and pi have none at all.
@nachoparker can you please help here? Why is NC stuck in maintenance every time NCP checks for NC updates (when the autoupdater is activated)? It seems strange to me that it actually switches to maintenance mode, just to check for a new version and discover that there is no new version. I can’t figure it out and can’t find any lines in the code (on github master where maintenance would ever be set), sorry. I couldn’t find an issue on github for that and I guess it is not a general bug, otherwise others would have reported that already.
Thanks for your assistance. Oh and Happy new year! Keep up the good work!
Can only see that webdav logins are failing
Your ncp.log I could not open with plain text editor
(xed has not been able to detect the character encoding. Please check that you are not trying to open a binary file.)
Best use pastbin.com or similar and post link here.
Has anybody else reported same issue anywhere?
Thanks for posting logs.
Yes there was an ncp-update last night, during which maintenance mode would be enabled, your log shows latest update was okay and maintenance mode disabled.
Finished code integrity check
Turned off maintenance mode
You updated using
Current Nextcloud version 126.96.36.199
Available Nextcloud version 15.0.0
NCP “production” users should really wait for NCP Devs to push update through nc-autoupdate-nextcloud. You can expect issues if you jump ahead. But yours seems to be fine now, or are you still having issues?