I am facing an upgrade problem from 23.0.2 to 23.0.3. When I open the updater, all steps are marked as successful:
Clicking the button “Update” shows the Button " [Go back to your Nextcloud instance to finish the update]" immediately, after some seconds the Nextcloud files page loads. This is the updater.log:
If he executes the command sudo -u www-data php /path/to/nextcloud/updater/updater.phar
there is perhaps another approach to solve the problem.
With the documentation the user knows that there are different update paths.
Thank you for your advice. I did not know about the CLI updater. But the result is the same, you see all steps are marked successful from the beginning:
~ $ sudo -u www-data php /var/www/nextcloud/updater/updater.phar
Nextcloud Updater - version: v20.0.0beta4-11-g68fa0d4
Current version is 23.0.2.
Update to Nextcloud 23.0.3 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-23.0.3.zip
Open changelog ↗
Steps that will be executed:
[✔] Check for expected files
[✔] Check for write permissions
[✔] Create backup
[✔] Downloading
[✔] Verify integrity
[✔] Extracting
[✔] Enable maintenance mode
[✔] Replace entry points
[✔] Delete old files
[✔] Move new files in place
[✔] Done
Continue update? [y/N] y
Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.
[✔] Check for expected files
[✔] Check for write permissions
[✔] Create backup
[✔] Downloading
[✔] Verify integrity
[✔] Extracting
[✔] Enable maintenance mode
[✔] Replace entry points
[✔] Delete old files
[✔] Move new files in place
[✔] Done
Update of code successful.
Should the "occ upgrade" command be executed? [Y/n] y
Nextcloud is already latest version
Keep maintenance mode active? [y/N]
Maintenance mode already disabled
Maintenance mode is disabled
The output from status.php:
{“installed”:true,“maintenance”:false,“needsDbUpgrade”:false,“version”:“23.0.2.1”,“versionstring”:“23.0.2”,“edition”:"",“productname”:“Nextcloud”,“extendedSupport”:false}
Communication occures to the download server: tcpdump shows an established session to download.nextcloud.com (IPv6/https).
@franz.hartwig
Please go in browser to this site of your nextcloud: https://cloud.server.tld/settings/admin/overview
and post the messages. Make a reload of the website.
running the update again manually is certainly useful advice. it’s a pity my complains only make it to the person doing some attempts to respond to the community
In your data folder, there is a folder for the updates: updater-xxxxxxx
the xxx are some random string. Within that folder you can find downloads. I’d check if there is perhaps an old version that you can manually delete.
If not, you can as well check the permission if the code belongs to www-data (but if there is a problem during one of the update steps, there should be an error).
I renamed the file .step, now the update works. After success update:
root@pi /nc/updater-51520bfa8e011 # cat .step
cat: .step: Datei oder Verzeichnis nicht gefunden [file or directory not found
root@pi /nc/updater-51520bfa8e011 # cat .step-previous-update
{"state":"end","step":10}
It seems the previous update left the file .step in place.
