Iâve been having problems updating from 19.0.6(.2 I believe) to 20.0.3.
The updater runs fine until it verifies integrity, then fails with:
Parsing response failed.
v Show detailed response
[nothing]
Observations:
No relevant log entries (neither in data/updater.log nor in the Settings -> Administration -> Logging)
Tested:
Clean update, removing data/updater-... entirely
Restoring previous 19.0.6 installation
Anyone else having similar issues?
PS: Not sure if this is the right category to post this into as it sounds to be reserved for first-time installations only (please let me know to move it).
Yes, I am having the same issue.
I clean up updater-xxxx folder in data directory and retry again and still the same.
Canât figure out what is causing it.
@tinkyx and anyone having the same issue: The problem is most likely the instance running out of memory. Raising PHPâs memory_limit to >=512M solved the issue in our case.
Let me know if you experience the same so I can mark this as the solution.
No, it doesnât work. Still the same. I have set memory limit to 512M and checked in nextcloud to make sure it is using 512M and it is. Then try to do update it still happens with that error. I was updating all the updates so far without any issue. I even updated to 19.0.6 and no issue, just after that there is an update for 20.0.3 so I try to update that too and the error started since then.
Might be worth doing some debugging. Have a look at my original post, Iâm linking to the source that defines the steps performed by the updater. Try setting some $this->silentLog("...") statements and monitor data/updater.log to see where the process fails.
Good to hear your case traces back to the same cause.
As to what youâre wondering, well Iâd assume some parameters have changed. I believe the routine calculating the downloaded binaryâs integrity runs out of memory (which looks like using openssl libraries); so, at a random guess, something in the routine or the libraries has changed that is affecting resource management, or maybe an increase of the input (file-size) has tripped a certain limit that now violates that certain <512MB memory threshold - it seems to be either one of those two.
Please feel free to mark my first reply as a solution; hopefully itâll help others as well!
I faced the same problem while trying to update through the web interface⌠My only solution was the manual upgrade approach through the shell⌠Only then did it work! Just in case this helps anyoneâŚ
No, I canât say I have, since I only found this thread after having upgraded the way I describeâŚ
I totally agree with you that updating the memory_limit is the predominant solution, yet I only wished to contribute here what worked for me after succesive failures with the web interface updater being stuck in âstep 5, verifying integrityâŚâ.
It intrigued me that there was no such problem with manually updating via the shell and I thought that I should add that to the discussion hereâŚI forgot to mention that my setup runs on an old RPi B+
Thank you all for your support and apologies if anyone mistook my answer as misleading!
Thanks for the additional detail - it helps to put things into perspective and distill things down to be as clear as possible - not that you had been confusing in any way in your previous post.
The Raspberry Pi 1 B+ has 512MiB by the looks of it, so one factor that allowed for success in your case. The crux in your case is (please correct me anyone if Iâm off here) that PHP is parameterized in what configuration it runs against - e.g. one system can have multiple configs and the runtime environment picks the one to use. I.e. the web updater would usually run PHP against the config the web server selects (e.g. the PHP installation usually has a config dedicated to Apacheâs use), while Nextcloudâs occ command probably (and Iâm not 100% certain here) runs against its own config, which might already be set to >=512M. Again - this is a guess and I might be wrong, but if thatâs how the Nextcloud updater is configured that could explain why you had success updating through the CLI and failed using the web interface.
Iâll do it for you.