Update always fails on verifying

[lfischer]

Hello,

I run a self hosted nextcloud version 30.0.11.1
The web updater always fails at step5 (Verifying integrity)
The reason might be the limited memory size of my hosting.

But in my understanding, the verification should be disabled:
integrity.check.disabled => true

Is there a way to skip this step?

Best,
Lars

[FredP]

Mine does this too.

Just hit the browser’s back button and restart the update. It should pick back up and then get through the verification quickly.

I think what happens is (at least for me) the download step takes a really long time, so I start the update then just walk away for a while. Since it doesn’t see any human interaction for some time, the security token expires (at least, there’s a message that says something along those lines).

[jtr]

@lfischer

But in my understanding, the verification should be disabled:
integrity.check.disabled => true

This is an undocumented config that disables checking the signatures of already installed apps / components. It is unrelated to the verification step in the Updater.

The Updater’s verification step checks that the downloaded archive file is not corrupted and is legitimate.

The reason might be the limited memory size of my hosting.

If your PHP memory limit is <= 256 MB, quite possibly. Though the v30.0.11 archive is still <256. This is more likely to be a problem with >= v31.

You can check your updater.log (it may have further details) and/or run the updater from the command line via updater.phar to see what is happening behind the scenes. Further details can be found in Updater - Nextcloud Server Admin Manual: Troubleshooting.

Is there a way to skip this step?

No, but you can always perform a manual update as described in the Admin Manual. Though since you’re on v30 I’m wondering if the cause is really something else, such as what @FredP mentioned.

[jtr]

@FredP

I think what happens is (at least for me) the download step takes a really long time, so I start the update then just walk away for a while. Since it doesn’t see any human interaction for some time, the security token expires (at least, there’s a message that says something along those lines).

Server PR #49578 may address this for you when it gets cleaned up and merged.

[FredP]

Ah very good!

[lfischer]

@FredP

Mine does this too.

Just hit the browser’s back button and restart the update. It should pick back up and then get through the verification quickly.

I think what happens is (at least for me) the download step takes a really long time, so I start the update then just walk away for a while. Since it doesn’t see any human interaction for some time, the security token expires (at least, there’s a message that says something along those lines).

This often happened to me for the backup step:
I usually have to delete the .step file to be able to re-run the update and the next time it was working fine in the past.
Now I have the first time the problem with the verification.

But I was able to find a workaround:

If the verification fails, the .step file contains something like “{“state”:“start”,“step”:5}”. Deletion of the file allows only to start the update process from the first step.
Now I changed the .step file content to “{“state”:“end”,“step”:5}”, which allows the update process to just continue with the next step after the verification.

Means problem solved for now.

[lfischer]

@jtr

@lfischer

But in my understanding, the verification should be disabled:
integrity.check.disabled => true

This is an undocumented config that disables checking the signatures of already installed apps / components. It is unrelated to the verification step in the Updater.

The Updater’s verification step checks that the downloaded archive file is not corrupted and is legitimate.

Thanks.

The reason might be the limited memory size of my hosting.

If your PHP memory limit is <= 256 MB, quite possibly. Though the v30.0.11 archive is still <256. This is more likely to be a problem with >= v31.

You can check your updater.log (it may have further details) and/or run the updater from the command line via updater.phar to see what is happening behind the scenes. Further details can be found in Updater - Nextcloud Server Admin Manual: Troubleshooting.

Is there a way to skip this step?

No, but you can always perform a manual update as described in the Admin Manual. Though since you’re on v30 I’m wondering if the cause is really something else, such as what @FredP mentioned.

I was able to find a workaround without the manual update:

If the verification fails, the .step file contains something like “{“state”:“start”,“step”:5}”. Deletion of the file allows only to start the update process from the first step.
Now I changed the .step file content to “{“state”:“end”,“step”:5}”, which enables the update process to just continue with the next step after the verification.

Means problem solved for now.

Thank you!