Hi there,
after updating manually to NC29.0.2 because the auto-updater failed I got the message that some files did not pass the integrity check.
The expected hash of the file core/doc/admin/_sources/configuration_server/domain_change.rst.txt does not match the hash of the existing file.
I already tried downloading NC 29.0.2 again and copy that file over the one with the invalid hash. But the message remains the same.
Does anybody have a clue how to get rid of this message?
Here is the exact output:
The following list covers which files have failed the integrity check. Please read
core
INVALID_HASH
core/doc/admin/_sources/configuration_server/domain_change.rst.txt
Array
)
)
)
jtr
July 16, 2024, 12:39pm
2
I already tried downloading NC 29.0.2 again and copy that file over the one with the invalid hash. But the message remains the same.
Did you click Rescan after replacing the file?
If so, and the problem remains, double-check how you’re uploading the replacement file. Hopefully you’re not using plain FTP, but if you are make sure it’s in binary mode (not ascii), for example.
after updating manually to NC29.0.2 because the auto-updater failed
I’d be interested in hearing more about how precisely the built-in Updater failed for you. There’s a dedicated log file called updater.log that may be helpful in troubleshooting.
Sorry, you are right I did not make sure to use binary mode in Filezilla.
I don`t have the updater.log anymore.
jtr
July 16, 2024, 1:13pm
4
The log is located in your datadirectory adjacent to your nextcloud.log. It should still be there.
Okay, found it. It just ends after deleting old files.
(https://download.nextcloud.com/server/releases/nextcloud-29.0.2.zip How to upgrade — Nextcloud latest Administration Manual latest documentation https://updates.nextcloud.com/changelog_server/?version=29.0.2
2024-06-20T18:15:00+0200 cxkJvsr8Yc [info] checkForUpdate() Arrayhttps://download.nextcloud.com/server/releases/nextcloud-29.0.2.zip https://docs.nextcloud.com/server/29/admin_manual/maintenance/upgrade.html https://updates.nextcloud.com/changelog_server/?version=29.0.2
2024-06-20T18:15:00+0200 cxkJvsr8Yc [info] getChangelogURL()Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-29.0.2.zip Open changelog https://updates.nextcloud.com/updater_server/ https://updates.nextcloud.com/updater_server/?version=28x0x6x1xxxstablexx2024-05-23T15%3A26%3A33%2B00%3A00+5481d81792b3eec0fddbb8bf56d78c1188519509x8x2x18 https://download.nextcloud.com/server/releases/nextcloud-29.0.2.zip How to upgrade — Nextcloud latest Administration Manual latest documentation https://updates.nextcloud.com/changelog_server/?version=29.0.2
2024-06-20T18:15:07+0200 OdRRQAFeBl [info] storage location existshttps://updates.nextcloud.com/updater_server/ https://updates.nextcloud.com/updater_server/?version=28x0x6x1xxxstablexx2024-05-23T15%3A26%3A33%2B00%3A00+5481d81792b3eec0fddbb8bf56d78c1188519509x8x2x18 https://download.nextcloud.com/server/releases/nextcloud-29.0.2.zip How to upgrade — Nextcloud latest Administration Manual latest documentation https://updates.nextcloud.com/changelog_server/?version=29.0.2
2024-06-20T18:15:14+0200 vXKRk3MMjt [info] storage location: /www/htdocs/…/…/web/cloud/data/updater-ocauigqeen1q/downloads/
jtr
July 16, 2024, 1:46pm
6
Since there are no errors after the download step, it’s possible it was a web server timeout if this was from running the Updater in web-mode.
To avoid that (as well as to capture any weird other errors that for some reason may not be logged), don’t use the offered update via the web UI. Instead run the Updater in command-line mode (next time you have an update to deploy). It will likely either work (by avoiding the web server timeouts) or, at the very least, provide some additional clues as to why it’s having difficulties in your environment.
Updater’s command-line mode docs: Upgrade via built-in updater — Nextcloud latest Administration Manual latest documentation
