Well, maybe that wasn’t such a great idea, after all… When I tried to update to 11.0.2, I got a “Parsing response failed. Step 4 is currently in process. Please reload this page later” error in step 4 : creating backup.
I managed to get back to original state by renaming /data/updater-ocrxxxxx/.step to OLD.step, then manually editing out my config file : ‘maintenance’ => true, to false and deleting the ‘updater.secret’ => ‘$2y$10$cSOexx……xxx’ line.
I will restore what I have removed (as mentioned in the first post) and report back.
Meanwhile, if you have any idea of anything else that might have caused this, I will gladly read it (bearing in mind that I have no access to ssh or root access, since I am on a shared hosting)
As stated before the backup dir is only used if the old state needs to be recovered. Feel free to delete after the update went successful and you notice no problems.
The .step file is usually removed during the occ upgrade or the web upgrader (the updater replaces code and the upgrader runs the actual migration steps of the new code).
So if you have problems with the updater just remove the whole updater-oc… directory and the updater doesn’t know anything anymore about any previous updater runs (which is fine if you don’t need the backed up code).
Ok then. I will try that. But I fear that he mishap that occurred in step 4 (creating backup) might happen at a later stage, like copying new files… Oh, well, I will try anyway, and restore backup if it fails.
Could you open the web developers tools during the upgrade and check the last request (once this happens) and send us the response. It seems that there is something going wrong while creating the backup.
I’m having the same issue with update from 11.0.2 → 11.0.3 using the updater.
First I get a failure message:
Create backup
Parsing response failed. 500 Internal Server Error
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@next.awequest.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Then when pressing “retry” I get the following:
Parsing response failed. Step 4 is currently in process. Please reload this page later.
Resetting seems to involve:
Getting out of maintenance mode: open /config/config.php and change the line 'maintenance' => true,
to 'maintenance' => false,
Removing the file: /data/updater-{rand-string}/.step
This allows me to try the updater again, but it has failed at least 3 times. There used to be a manual way to backup and proceed on earlier versions. Is that still an option? Obviously the direct method via the browser would be best, but I’m open to alternatives.
Running no shared hosting environment (which could be the cause of issues, uncertain). Happy to provide whatever I can to troubleshoot.
Dumb question: Is there actually enough space to create a full backup including zip download before? Or to the developers: Would there be a meaningful error response if this was the case?
Copy config.php, potentially changes to .htaccess, themes and 3rd party apps back from backup. Or better install 3rd party apps fresh from app store, if no manual changes to some info.xml was made.
Move data folder back in place, if it was actually inside nextcloud folder.
(bearing in mind that I have no access to ssh or root access, since I am on a shared hosting)
