Update from 27.1.4 to 27.1.5 does nothing

I triet to update my NC instance from 27.1.4 to 27.1.5 but the updater does “nothing”.
It does not matter if I try to update via web frontend or from command line, the updater runs without any error messages and says that everything has been done - but in actually it does nothing.
The version after the “update” is still 27.1.4 and it also tells me that there is an update available.

There is nothing about the updater in the logs.

So what’s going on?

Here’s the output of a command line based update try:

~/www/nextcloud # php updater/updater.phar
Nextcloud Updater - version: v27.1.0rc3-15-gfa7af53

Current version is 27.1.4.

Update to Nextcloud 27.1.5 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-27.1.5.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] n
Maintenance mode already disabled

Maintenance mode is disabled
~/www/nextcloud # php ./occ --version
My-Cloud 27.1.4
~/www/nextcloud # php --version
PHP 8.2.14 (cli) (built: Dec 21 2023 20:18:00) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.2.14, Copyright (c) Zend Technologies
    with the ionCube PHP Loader v13.0.2, Copyright (c) 2002-2023, by ionCube Ltd.
    with Zend OPcache v8.2.14, Copyright (c), by Zend Technologies

All that at a shared hoster using some Debian distribution; database is a mariadb version.

In the past the update worked, though…

It sounds like the .step folder may not be getting cleaned up for some of you after each update/upgrade cycle for some reason.

You can remove it manually, (as noted in other posts here), but the safest is to run occ maintenance:repair which should accomplish the same thing (along with some other things that shouldn’t hurt).

Of course always have backups before doing updates/upgrades.

If it re-occurs, check your data/updater.log file.

1 Like

Thanks - I executed “maintenance:repair” - after that the .step folder was no longer present and the update worked!

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.