Well here I am again. Ran the latest update and poof …it messed up and now I am left with “Update in process.” Message.
I am left (I think) in maintenance mode: on and trying to figure out how to turn it off.
All of the searches give me is “sudo -u www-data php /var/www/nextcloud/occ maintenance:mode --off” which doesn’t work.
Sit rep:
Nextcloud upgrade to latest version 18.
Running latest Unraid 6.8.2
Hardware: Dell R710
Self hosted.
The log files show that the update is done (I think).
I have run into this every time I upgrade to the next version. I can’t remember how to fix this from the last time. Been at it all day - the insanity is that I knew this would happen…
I am tired and giving up for the day … makes me wanna move to a less complicated solution.
If you have any suggestions and they work I promise I will document it for the next time - oh and there will be a next time I am sure.
Unfortunately this comes with the territory with these types of systems. Lots of variables from one system to the other, this is why many projects have switched to things like docker to reduce the variability between systems. Hope you had a good vent either way
Now for some potentially helpful notes:
If updates halted mid update you should probably attempt to re-run them via the terminal
If you just need to disable the maintenance mode you can manually edit the config.php and change the line 'maintenance' => true, to 'maintenance' => false,
As you are your own systems administrator you make sure to do your own backup prior to any update.
NOTE: The updater makes a backup as well, you will find that in the data folder data/updater-ocry####. I’ve never used this for a restore personally.
EDIT: I should note I never use the web updater and instead run this in terminal as I tend to encounter time-out issues. This has to do with my php setup and I have never bothered to fix it
It functions no problem. Just can’t get to OCC or anything else to complete the install (I think it is done) just need to get out of maintenance mode I think.
I did use updater (stoopid me) and I got the usual timeouts.
Well, as usual it didn’t take long for the knives to come out.
Really disappointed - again.
I really do ask dumb questions (not knowing their dumb but wait for users like Henry to point that out).
Just starting out with Nextcloud and have had some limited success.
I really didn’t post here to be abused or berated by the Nextcloud gods (legends in their own minds).
Thanks to users dugite-code. Gatak and I think rakeniven (although not really sure) for an honest attempt to assist me. You folks do make it welcoming and try to help.
I will going elsewhere for answers - oh and Henry I have a movie I want you to watch - you will love it - its all about you … https://www.imdb.com/title/tt10011682.
I will post back the solution so that it might help others. Which is what this is supposed to be all about.
The pictures look like WinSCP, so Windows is probably a good guess.
@toolmanz Don’t get demotivated by people like him. There’ll be always someone who is putting a pinch of sarcasm somewhere.
Back to topic:
If it’s a docker container, you need to either access the docker container via SSH first and use the occ command (i.e docker exec -it <container name> /bin/bash) or you can execute the occ command from outside the docker by sending the command to that docker container (i.e docker exec <container name> '/var/www/nextcloud/updater/updater.phar')
No, the problem is that you have no idea how Docker works, but you blame Nextcloud for it. Docker works inside the container with its own user. A user that is not recognized by your host system and therefore prints as nobody. This is quite normal under certain circumstances and also the reason why you should work inside the docker container.
Docker works inside the container with its own user. A user that is not recognized by your host system and therefore prints as nobody. This is quite normal under certain circumstances and also the reason why you should work inside the docker container.