Stuck on update process. Step 5 is currently in process. Please reload this page later

This topic already asked in February 2018 but nobody replied. Im am stuck on upgrading from v 16.0.1.1 to v 16.0.4. Message:

Step 5 is currently in process. Please reload this page later.

I waited for about one week now and tested it several time, no change. I always get this message when clicking again on “open Updater”.

configuration:
PHP: 7.1.30
mysql: V5.7.26
Operating system: Linux 4.4.0-159-generic #187-Ubuntu SMP Thu Aug 1 16:28:06 UTC 2019 x86_64

Is there a possiblity to get this running without doing a complete new installation?
Is it worth waiting for the next version, so the update will start with the new version ignoring the update process it got stuck.

Thanks

I think there is a “steps” file in your NC folder and every update attempt will continue with the step mentioned in that file. So waiting and retrying won’t help probably.

Can you post some logs here? With only that this error message it is impossible to give helpful answers to you.

We need the updater.log, maybe the nextcloud.log and please provide the output of ls -al of your nextcloud installation directory. If you can see any file containing “step” in its name, please provide the output of this file as well.

Hi Schmu,

thank you for your quick response.

I do not have command line access to my NC installation, only ftp. So I cannot do a ls -al or any other linux command.

I searched for the updater.log and nextloud.log. Too much lines to post all of them here.

I got some additional information from these files. NC Update shows me that he can install the stable 16.0.4, but during the update process 16.0.3.0 is downloaded. This zip file (nextcloud-16.0.3.zip) is under /cloudXXX/data/updaterXXX/downloads.

So the reason for this issue might be that the update expects another zip file.

Screenshot from the version showed me on the admin page:

nc
(sorry its in german)

Might it be a solution to download 16.04 manually, move it via ftp to the download folder and try to go on with the update?

Thanks

here some lines from updater.log. No line deleted but some signatures and paths. I also had to delte the https because I am a new user, replaced it with LINK. (Only 4 links allowed)

2019-08-11T11:58:22+0200 [info] request to updater
2019-08-11T11:58:22+0200 [info] currentStep()
2019-08-11T11:58:22+0200 [info] show HTML page
2019-08-11T11:58:22+0200 [info] current version: 16.0.1 build time: 2019-05-15T14:42:44+00:00
2019-08-11T11:58:22+0200 [info] getUpdateServerResponse()
2019-08-11T11:58:22+0200 [info] updaterServer: LINK://updates.nextcloud.com/updater_server/
2019-08-11T11:58:22+0200 [info] releaseChannel: stable
2019-08-11T11:58:22+0200 [info] internal version: 16.0.1.1
2019-08-11T11:58:22+0200 [info] updateURL: LINK://updates.nextcloud.com/updater_server/?version=XXXX
2019-08-11T11:58:22+0200 [info] getUpdateServerResponse response: Array
(
[version] => 16.0.3.0
[versionstring] => Nextcloud 16.0.3
[url] => LINK://download.nextcloud.com/server/releases/nextcloud-16.0.3.zip
[web] => LINK://docs.nextcloud.com/server/16/admin_manual/maintenance/upgrade.html
[changes] => LINK://updates.nextcloud.com/changelog_server/?version=16.0.3
[autoupdater] => 1
[eol] => 0
[signature] => XXXXXXXXXXXXX
)

2019-08-11T11:58:22+0200 XXXXXXXXXX [info] checkForUpdate() Array
(
[version] => 16.0.3.0
[versionstring] => Nextcloud 16.0.3
[url] => LINK://download.nextcloud.com/server/releases/nextcloud-16.0.3.zip
[web] => LINK://docs.nextcloud.com/server/16/admin_manual/maintenance/upgrade.html
[changes] => LINK://updates.nextcloud.com/changelog_server/?version=16.0.3
[autoupdater] => 1
[eol] => 0
[signature] => XXXXXXXXXXXXXXXXXXX
)

2019-08-11T11:58:22+0200 [info] getChangelogURL()
2019-08-11T11:58:22+0200 [info] end of checkForUpdate() Update to Nextcloud 16.0.3 available. (channel: “stable”)
Following file will be downloaded automatically: LINK://download.nextcloud.com/server/releases/nextcloud-16.0.3.zip
Open changelog ↗
2019-08-11T11:58:24+0200 [info] request to updater
2019-08-11T11:58:24+0200 [info] currentStep()
2019-08-11T11:58:24+0200 [info] POST request for step “1”
2019-08-11T11:58:24+0200 [info] startStep(“1”)
2019-08-11T11:58:24+0200 [info] checkForExpectedFilesAndFolders()
2019-08-11T11:58:24+0200 [info] end of checkForExpectedFilesAndFolders()
2019-08-11T11:58:24+0200 [info] endStep(“1”)
2019-08-11T11:58:24+0200 [info] request to updater
2019-08-11T11:58:24+0200 [info] currentStep()
2019-08-11T11:58:24+0200 [info] Step 1 is in state “end”.
2019-08-11T11:58:24+0200 [info] POST request for step “2”
2019-08-11T11:58:24+0200 [info] startStep(“2”)
2019-08-11T11:58:24+0200 [info] checkWritePermissions()
2019-08-11T11:58:24+0200 [info] end of checkWritePermissions()
2019-08-11T11:58:24+0200 [info] endStep(“2”)
2019-08-11T11:58:24+0200 [info] request to updater
2019-08-11T11:58:24+0200 [info] currentStep()
2019-08-11T11:58:24+0200 [info] Step 2 is in state “end”.
2019-08-11T11:58:24+0200 [info] POST request for step “3”
2019-08-11T11:58:24+0200 [info] startStep(“3”)
2019-08-11T11:58:24+0200 [info] createBackup()
2019-08-11T11:58:50+0200 [info] end of createBackup()
2019-08-11T11:58:50+0200 [info] endStep(“3”)
2019-08-11T11:58:50+0200 [info] request to updater
2019-08-11T11:58:50+0200 [info] currentStep()
2019-08-11T11:58:50+0200 [info] Step 3 is in state “end”.
2019-08-11T11:58:50+0200 [info] POST request for step “4”
2019-08-11T11:58:50+0200 [info] startStep(“4”)
2019-08-11T11:58:50+0200 [info] downloadUpdate()
2019-08-11T11:58:50+0200 [info] getUpdateServerResponse()
2019-08-11T11:58:50+0200 [info] updaterServer: LINK://updates.nextcloud.com/updater_server/
2019-08-11T11:58:50+0200 [info] releaseChannel: stable
2019-08-11T11:58:50+0200 [info] internal version: 16.0.1.1
2019-08-11T11:58:50+0200 [info] updateURL: LINK://updates.nextcloud.com/updater_server/?version=XXXXXXX
2019-08-11T11:58:51+0200 [info] getUpdateServerResponse response: Array
(
[version] => 16.0.3.0
[versionstring] => Nextcloud 16.0.3
[url] => LINK://download.nextcloud.com/server/releases/nextcloud-16.0.3.zip
[web] => LINK://docs.nextcloud.com/server/16/admin_manual/maintenance/upgrade.html
[changes] => LINK://updates.nextcloud.com/changelog_server/?version=16.0.3
[autoupdater] => 1
[eol] => 0
[signature] => XXXXXXXXXXXXXXXXXXXX
)

2019-08-11T11:58:51+0200 [info] storage location exists
2019-08-11T11:59:46+0200 [info] end of downloadUpdate()
2019-08-11T11:59:46+0200 [info] endStep(“4”)
2019-08-11T11:59:46+0200 [info] request to updater
2019-08-11T11:59:46+0200 [info] currentStep()
2019-08-11T11:59:46+0200 [info] Step 4 is in state “end”.
2019-08-11T11:59:46+0200 [info] POST request for step “5”
2019-08-11T11:59:46+0200 [info] startStep(“5”)
2019-08-11T11:59:46+0200 [info] verifyIntegrity()
2019-08-11T11:59:46+0200 [info] getUpdateServerResponse()
2019-08-11T11:59:46+0200 [info] updaterServer: LINK://updates.nextcloud.com/updater_server/
2019-08-11T11:59:46+0200 [info] releaseChannel: stable
2019-08-11T11:59:46+0200 [info] internal version: 16.0.1.1
2019-08-11T11:59:46+0200 [info] updateURL: LINK://updates.nextcloud.com/updater_server/?version=XXXXXXX
2019-08-11T11:59:46+0200 [info] getUpdateServerResponse response: Array
(
[version] => 16.0.3.0
[versionstring] => Nextcloud 16.0.3
[url] => LINK://download.nextcloud.com/server/releases/nextcloud-16.0.3.zip
[web] => LINK://docs.nextcloud.com/server/16/admin_manual/maintenance/upgrade.html
[changes] => LINK://updates.nextcloud.com/changelog_server/?version=16.0.3
[autoupdater] => 1
[eol] => 0
[signature] => XXXXXXXXXXXXXXXXXXXX
)

2019-08-11T11:59:46+0200 [info] storage location: /www/htdocs/XXXXXX/XXXXXXXXXXXX/data/updateXXXXXX/downloads/
2019-08-11T11:59:57+0200 [info] request to updater
2019-08-11T11:59:57+0200 [info] currentStep()
2019-08-11T11:59:57+0200 [info] Step 5 is in state “start”.
2019-08-11T12:01:24+0200 [info] request to updater
2019-08-11T12:01:24+0200 [info] currentStep()

last 3 lines repeat several times.

Possible, yes. Unfortunately the log doesn’t tell what is actually bugging the updater.
When did you try the update the last time? Are the log entries the very latest ones?
I’m asking because of the timestamps from the logs: 2019-08-11

Date and time are set correctly on your server, right?
Can you visually check for the step file via FTP with hidden files shown? It might be a solution to delete this file in order to make the updater start with step one again and download the latest NC version instead of the previous one.
I believe the step file is named “.step” (so hidden) and is placed in the updater folder. Please look for it, it must be somewhere, then create a backup of that file (move it somewhere else) and retry the web updater.

Date and time are correct, I only deleted these lines because they are always the same, last entry in update.log:

2019-08-18T12:22:09+0200 [info] request to updater
2019-08-18T12:22:09+0200 [info] currentStep()
2019-08-18T12:22:09+0200 [info] Step 5 is in state “start”.

I found the .step, content:
{“state”:“start”,“step”:5}

I started the update again, if I look into the download directory the correct version (16.0.4) is there. If I start the updater again I come up to this step:
nc_update_download

After I click on back and restart the updater I am back to the error message from the thread header.

I googled using this new information and found:

and

None of them worked. Any ideas how I get this inegrity check passed?

Thanks

Hi Wiggum23,

I was stuck on the same error for step 5. Under nc/updater/index.php i edited line 1338-1340 on mine and removed

		case 5:
			$updater->verifyIntegrity();
			break;

Removed this skipped the check and installed just fine. Let me know if this helps.

Sorry for responding late.

I searched around a bit today because there must be a reason for this error. There were some new information in another thread I tested.

I entered in the .htaccess (root directory, not the one under config)

php_value memory_limit 256M

Below the line

DO NOT CHANGE ANYTHING ABOVE THIS LINE

And now it worked fine.

Thanks for all your help.