(Update did not run smoothly, i had to disable an app i coded myself (and whitch was supposed to be entirely disabled and removed, but it wasn’t apparently)):
To disable my own plugin qrcode_generator, i ran these mariaDB commands:
USE ownclouddb
UPDATE oc_appconfig
SET configvalue = ‘no’
WHERE appid = ‘qrcode_generator’ AND configkey = ‘enabled’;
After that, update was a sucsess and after the update, i could access owncloud with all my files, but i noticed that the integrity check failed, because of “core”
Expected behaviour
There shouldn’t be any error messages and the integrity check should be completed without any error
Actual behaviour
The integrity check failed with this error message: https://pastebin.com/nXcSKLgu
Server configuration
Operating system:
Ubuntu 24.04 Web server:
Apache 2 Database:
MariaDB PHP version:
I believe 7.4 ownCloud version: (see ownCloud admin page)
10.15.0.2 Updated from an older ownCloud or fresh install:
updated Where did you install ownCloud from:
originally through an install script, but everything worked just fine before the update Signing status (ownCloud 9.0 and above):
?
Again, the link to the failed integrity check: https://pastebin.com/nXcSKLgu
The content of config/config.php:
https://pastebin.com/tLZSQEMi
Are you using external storage, if yes which one: local/smb/sftp/…
no
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
I updated via web updater and the same thing happened to me.
There seems to be no malfunction, but the error message is a bummer.
Can not upload my error logs since writing a link or uploading a file is not allowed for me, but
I just confirmed that INVALID_HASH files list and hashes are exactly the same as OP and mine.
I haven’t found anything that isn’t working, so to get rid of the notification, i just disabled the integrity check. In the config.php, I just added this line: 'integrity.check.disabled' => true,
i did an manual update to ownCloud 10.15.0 recently (which i think is the suggested / recommended way) and i haven’t noticed such messages. Maybe it could be possible that this problem only happening with the updater app? If this is the case then i think it could be possible that it is required to let the ownCloud people know about this over here:
Hi there,
I have also used the updater app and the integrety check only fails on the files of the updater app (see below). I assume something went wrong in the process of building the updater app. It would be great if this could be fixed quickly to get rid of this message. I would also be glad, to receive a confirmation, that it really is an process error and not due to a malware attack that manipulated the updater package.
Here is the output of the integretiy check:
Technical information
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
i think for this some one would need to create an issue for the ownCloud people like i mentioned previously. I think i have read somewhere here in the forums that the ownCloud people are not necessarily looking into this forums and could not notice it. Only i an GitHub issue is raised i think the changes are high that a quick fix is provided.
Thank You very much for Your proposal - in fact I did exactly that and an issue is filed under the number #749. I am not allowed to include the link to https://github.com/owncloud/updater/issues/749