Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(hosted service) Update stuck on Step 3 #182

Closed
nr458h opened this issue Sep 1, 2018 · 10 comments
Closed

(hosted service) Update stuck on Step 3 #182

nr458h opened this issue Sep 1, 2018 · 10 comments

Comments

@nr458h
Copy link

@nr458h nr458h commented Sep 1, 2018

Hi all.

I have a NC Installation on a hosted service with only access to Nextcloud itself.

In the past all updates went fine (from 12 - > 13) but when I tried to update from 13.05 to 14 RC 1 Everything went fine till step 3. Now it always shows
Step 3 is currently in process. Please reload this page later.

Is there any way to restart or aboard the installation through the GUI? Or where can I point the support to solve this problem?

Thanks in advance

@23n

This comment has been minimized.

Copy link

@23n 23n commented Sep 17, 2018

Via FTP:
Try to delete the .step file located here:
yournextcloud/data/updater-"randomstring"/.step

"randomstring" is something like nc5kbpv4n4a5 or whatever, added by the updater
(i.g. ../updater-c5kbpv4n4a5/.step)

@nr458h

This comment has been minimized.

Copy link
Author

@nr458h nr458h commented Sep 21, 2018

Thanks for the hint, worked well!

@nr458h nr458h closed this Sep 21, 2018
@mlopezcoria

This comment has been minimized.

Copy link

@mlopezcoria mlopezcoria commented Nov 26, 2018

Via FTP:
Try to delete the .step file located here:
yournextcloud/data/updater-"randomstring"/.step

"randomstring" is something like nc5kbpv4n4a5 or whatever, added by the updater
(i.g. ../updater-c5kbpv4n4a5/.step)

Thank you! I had the same issue and this solved it.

@grisu48

This comment has been minimized.

Copy link

@grisu48 grisu48 commented Dec 11, 2018

The same happened to me. I just had to wait a little bit (went for a cup of coffee), restarted the updater and could resume from step 3.

No need to delete the .step file. Still the process was unpleasant: Initially I assumed the installed instance crashed.

@ossadmirer314

This comment has been minimized.

Copy link

@ossadmirer314 ossadmirer314 commented Mar 5, 2019

Same here: "Step 3 is currently in process. Please reload this page later."
Message remains, this is a bug...
3 times refeshed after some minutes. no effect.
There is no *.step file to delete
see log:
...
2019-03-05T14:56:54+0100 eMcL6sBLCq [info] currentStep()
2019-03-05T14:56:54+0100 eMcL6sBLCq [info] Step 3 is in state "start".
...
repeating entries

@ossadmirer314

This comment has been minimized.

Copy link

@ossadmirer314 ossadmirer314 commented Mar 5, 2019

and now found message after found and deleted .step files:

Create backup
Parsing response failed. <title>500 Internal Server Error</title>

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at [no address given] to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.


Apache Server at xxxxxxxxx.de Port 443

@grisu48

This comment has been minimized.

Copy link

@grisu48 grisu48 commented Mar 6, 2019

I had the same issue when upgrading vom 14.0.4 to 15.0.5. For me waiting a little bit longer solved the issue. Was stuck in Step 3, then in frustration I took a cup of coffee, returned quarter hour later, re-opened the updated and I could resume from that point.

@daniu-de

This comment has been minimized.

Copy link

@daniu-de daniu-de commented Apr 10, 2019

Hi,
I am having that issue on EVERY update of nextcloud - sometimes more than once ...
regards

@xydac

This comment has been minimized.

Copy link

@xydac xydac commented May 17, 2019

With nginx update config at least below:
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 600;

@towhereur

This comment has been minimized.

Copy link

@towhereur towhereur commented Jan 14, 2020

@xydac in case using nginx as proxy of apache server.
In my case, nginx is one-and-only web server and upgrade from 17.0.0.9 to 17.0.2. data folder size is about 50GB.
On updater page, backup took me about 15 min. so 600 is not enough, so I set it to 1200(1000 would be ok I guess).

there are two files to modify. (nginx conf and php.ini)

nano /etc/nginx/conf.d/nextcloud.conf

location ~ ^/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|updater/.+|ocs-provider/.+|core/templates/40[34]).php(?:$|/) {
fastcgi_read_timeout 1200;
}

nano /etc/php/7.2/fpm/php.ini

max_execution_time = 1200

service nginx restart

#One more thing
if you have .step file in below folder, delete it. nextcloud- folder in backups folder, delete it.
/usr/share/nginx/nextcloud/data/updater-/

Open updater page and run update.
Hope it helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants
You can’t perform that action at this time.