I figured no harm in trying 10.0.2 for nowā¦ update appeared to be smooth and no issues reported in admin/nothing showing in the log.
Reassuringly underwhelming
I figured no harm in trying 10.0.2 for nowā¦ update appeared to be smooth and no issues reported in admin/nothing showing in the log.
Reassuringly underwhelming
same here - all went smooth.
As always, donāt forget to manually re-enable all apps that have been disabled during upgrade:
for i in calendar contacts notes ojsxc ownnote polls richdocuments tasks; do php occ app:enable $i ; done
Just done now 10.0.1 ==> 10.0.2 with the web updater without any glitches. All went smooth. Very good work guys !
Wow update with the updater worked fine at 2nd try!
1st try showed error, because it couldnāt write to the updater directory.
sudo chown -R www-data:www-data /var/www/owncloud
fixed istā¦
Thank You!
Same here. Would be nice if the updater learned to change permissions he needs and change them back to a safe default
Updater did not work for me.
First it complained about the folder āassetsā being present, then about not being able to write to the āupdaterā folder. My permissions on ALL folders were set as suggested per https://docs.nextcloud.com/server/10.0/admin_manual/installation/installation_wizard.html#strong-perms-label
Apparently these settings are not compatible with the updater. Did a manual (backup &) update as per a modified version of the script suggested here: Shell script for backup and upgrade (nextcloud or owncloud)
That would require the updater run with elevated privileges. Not good.
Did not run through for me as well. After being stuck for half an hour on copying in the new files, I went to /config/config.php and set āmaintenanceā => false. After that, the update started or maybe ran a 2nd time. That I could not tell. After that all was fine.
Then this must be made clear in the Updater Startpage. Otherwise itās just confusing.
Thatās right. And doing -R www-data:www-data /var/www/nextcloud isnāt complicatedā¦
Updater tells me he found an unexpected file ātmpā ā well, there should be a folder tmp but isnĀ“t that supposed to be there or did I put it in the wrong place?
thx
Initializing
Current version is 10.0.1.
Update to Nextcloud 10.0.2 available. (channel: āstableā)
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-10.0.2.zip
Retry update
Check for expected files
The following extra files have been found:
tmp
in my installation it gives the same behavior, but with directory userappsā¦
It seems there a still migration issues from owncloud 9.1:
Well, I tried to update from 10.0.1 (stabel and beta) channel to 10.0.2.
However I always received the Error message: Cannot use updater, please use manual update!
it was promised, that from 10,0.1 on, you can use the built-in updater!
if it does not work at all, What is the use for it???
I am getting sick and tired to hassle around with the manual update !!!
Regards, hitam4450
I donāt see that error message anywhere in our source code. Please post the complete original error message!!! Thanks
Error message:
Could not start updater, please try the manual update
After That, i am urged to download 10.0.2 manually!
I tried using the updater to update from 10.0.1 to 10.0.2. First try I had an āopen_basedirā permission error as I only added "/srv/www/nextcloudā and not ā/srv/wwwā. After fixing this it worked fine. When the updater was done (all checkmarks) I switched āmaintenance_modeā off and clicked on the link saying āgo back to your nextcloud instanceā. Then I was greeted with a āUpdate needed - Please use the command line updater because you have a big instance.ā though.
Edit: Next I ran the āupdater.pharā and everything was fine again. Thanks.
Can anybody tell me if I put ātmpā in the wrong location or if I should just delete it to run the update and then reopen the folder - or should I better wait for a revised updater?
Hi, I tried the updater from 10.0.1 to 10.0.2 on a raspberry pi setup with nginx, it does not work.
On another setup (webhoster, apache) everythink worked well.
Is there anything I can do to make the updater work with my nginx setup?
Best regards, Stefan