After updating the Server version, I had to update the PHP version in the installation of Ubuntu 14.04 where I have Owncloud installed, because I got a message that the PHP version should be at least 5.6.
I have installed PHP 7.1 and configured Apache2 to activate the new version of PHP and when accessing Owncloud I get these lines:
Perfect!
The Owncloud X is running… but appears a yellow banner in the top of the web “There were problems with the code integrity check. More information…”
There are 2 messages in red:
The blocking transactional locking file should be configured to use memory-based blocking, not slow database-based blocking.
(I follow the instructions to disable “File Locking” app but it’s not installed)
I have read the documentation referring to the error, but they are many many affected files and I do not know if it is something that affects the installation massively.
In this documentation, it explains each case:
FILE-MISSING: In principle I would have to recover them, but I do not know from where.
INVALID-HASH: There are 123 files modified after signing them digitally: I do not know how to solve this.
EXTRA-FILE: theoretically these 44 files could be deleted, because they are not in the file signature.json
In the documentation it puts a warning in red: Please don’t modify the mentioned signature.json itself.
I do not dare to do any editing of this file.
In the ownCloud core (that is, the ownCloud server itself) the files “index.php” and “version.php” do have the wrong version.
Solution:
Upload the correct “index.php” and “version.php” files from e.g. the archive of your ownCloud version.
which is probably valid for the “FILE_MISSING” as well (if a file missing you need to upload it the same way you need to fix an wrong version of a file).
Yes, and thats why you should delete these files (not the signature.json) as explained in the documentation as well:
Reason:
In the ownCloud core the unrequired extra file “/test.php” has been found.
Solution:
Delete the “test.php” file.
For me it looks like the documentation provides all required information on how to solve this issue.
Thanks for your help, but i think this: I check that almost all the files affected by the integrity are from the updater folder. I gather that the problem has coming in the update process.
I suppose that in the next update, if done correctly, this warning may disappear.
Yes. That’s what I thought.
But in the repository of OwnCloud versions I can not find for the Ubuntu 14.04 version.
I do not know if extracting the files of the version for Ubuntu 16.04 I will have more problems later…
I would give it a try, but SAVE the current updater folder first!. What can happen is, that afterwards your owncloud instance still has a non-working updater.
Use the last installed/upgraded owncloud package. I think, you should have a copy in your apt cache, but I’m not very familiar with ubuntu systems.
I have done what you told me to replace the updater folder with the original package of version 10.0.10 and no warning appears.
Thank you all for the great help you have given me.