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

🚧 Installation
28

Thanks for your proposal, was the only way to leave the blocking state. :+1: Top

29

I have the same situation as @Darkluke, one nextcloud instance is running at a rented webspace.
The maxiumum available php-memory limit is there 128M.
The web updater is downloading the nextcloud *.zip file.
If this zip file is larger than the php-memory limit (in my case > 128M) the verify process will fail and the installer stops and hang in step 5.
e.g. nextcloud-20.0.7.zip = 123MB filesize → working :heavy_check_mark:
e.g. nextcloud-20.0.4.zip = 136MB filesize ->not working :x:

If failing you should verify the zip download yourself and then use this workaround:

@NextcloudDevelopers: If you switch from zip to tar.bz2 we will have a longer time nextcloud fun with our rented webspaces and 128M memory limit :pray:

2 Likes
30

Thank you. Deleting the updater-xxxxx directory form the data directory did the trick. Once again, many thanks.

1 Like
31

This worked for me. Renaming the .step file did it. I renamed mine to “.step_old”

32

I did both steps and the update went well.
After that I realized that the entry in .htaccess is gone. The file seems to have been rewritten by the updater.

Regards,
Thomas

33

Thanks, Danfro, for your mod of the suggestion by @dshirk . Renaming the .step file worked for me on 2021-05-06 for the upgrade to 20.0.9. Replying with this in case anyone else needs it!

1 Like
34

Great. Glad I could help. :+1:

For everyone still stuck at this step, one more addition from my recent experience:

The update seems to stuck on the validation process of the downloaded file. Although php memory may seem to cause this failure if set too low, this is not the only cause.

I recently had this with the memory limit set to 1 GB. I tried deleting the .step file several times - without success.

What did finally work? Just waiting a day. :wink: The next day, after deleting the .step file, it went through without errors.

So my guess is, the validation process might fail because the server can not cope with the data load at certain times. Waiting some time for a less busy time can be all it needs. This would also explain why this error keeps coming up throughout releases. So the next time you are stuck there, get yourself a cup of coffee, relax and come back later. :slight_smile:

35

Renaming the .step to .step_old did the trick for me, I was able to update from ver 21.0.0 to 21.0.1 thank so much guys!

1 Like
36

None of the things above helped me so here is my solution:

go into the file /var/www/nextcloud/updater/index.php and comment the lines:

    if($stepState === 'start') {
            die(
            sprintf(
                    'Step %s is currently in process. Please reload this page later.',
                    $stepNumber
                    )
            );
    }

with “//” at the beginning out.

Reload your Update-Page - done!

5 Likes
37

Thanks for sharing, it’s worked.

38

fokin legend

39

try to find the step file using find command, something like:
find / | grep .step
and then rename or delete the .step file

1 Like
41

Thanks to all that gave answers in this thread - it worked for me too!
I only had to:

  • Set the php memory limit to 512M in php.ini
  • Remove the old updater-oc3phxvt6byt directory from the data directory.
42

To avoid rewriting:
Maybe this is a solution which worked for me -

PHP-Speichergrenze einstellen

Geschickter ist es im gleichen Ordner die versteckte Datei “.user.ini” um folgende Zeilen zu erweitern:

memory_limit=512M
max_execution_time=7200

Sieht dann so aus:

mbstring.func_overload=0
always_populate_raw_post_data=-1
default_charset=‘UTF-8’
output_buffering=0
memory_limit=512M
max_execution_time=7200

https://www.andysblog.de/nextcloud-bei-all-inkl-com-installieren

Support Ukraine
Bernd

43

I think that worked for me too, hosted on all-inkl (Germany).
I deleted all stuff from “updater-xyz123” in /nextcloud/data, follow your tip and in the first time it stuck again at the same point. But after reloading the updater page two or three times, the progress going forward until the end.

44

I’ve just got the same issue updating from 23.0.5 to 24.0.1 and this hack helped to finish the update. Thanks! It’s a shame that NC devs couldn’t fix this bug for 3 years.

45

This worked for me. Worth noting that I did NOT have a /data/updater-xxxxx/ directory.

46

It is as amarus describes. And the issue is, that you need to

  • add the line after avery update in -htaccess
  • and also delete the old update folder in data.
47

there is no old update leftovers in my data folder… can u help?

48

Same for me, awesome