Closed ghost closed 8 years ago
It does show a sha512-sum for your files. But the files are not supposed to be there, for a non-existing file, there can't be an "expected"-hash (or it would be empty)! The last version you run was 9.0.0 or 8.2.3?
Did you at any point install files manually into the ownCloud folder? The only way I can see this occurring is if old files from a previous installation remained after the package update, but apt should prevent that...
@jnweiger Any idea?
Nope, I only tinkered with the config.php.
On April 9, 2016 5:19:24 AM MDT, Robin McCorkell notifications@github.com wrote:
Did you at any point install files manually into the ownCloud folder? The only way I can see this occurring is if old files from a previous installation remained after the package update, but apt should prevent that...
@jnweiger Any idea?
You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/owncloud/core/issues/23876#issuecomment-207771593
Apologies, I got it backwards! I'll edit the title to show that the expected sum is blank, not the calculated sum.
I just upgraded from 9.0.0 to 9.0.1 yesterday in hopes that it fixed it. I've more or less followed each update pretty closely for security updates.
I looked through my logs: While I thought I was using the official repositories earlier than this, my apt logs suggest that 8.1.0-3 was the first version that I installed. Before that I was manually installing/upgrading starting from around OC 5 or 6, I think.
I'm pretty certain that I made a point to blow away the old owncloud directory and copy only the config.php over from the manual installation to prevent any issues. The data directory (mounted on /home/owncloud) remained untouched.
@ainola That would explain why you are seeing these issues then - for example, settings/settings.php
was only in oC 8.0, but was removed in oC 8.1, so perhaps when you installed from the repositories you forgot to clear out the old ownCloud directory.
I'm could have sworn I renamed the old directory to owncloudBAK before installing the package, then moved the config.php file manually to config/config.php. I guess I was wrong.
It was indeed leftover files all over the place. I diffed a new install to my current one and there were lots of files that shouldn't have been there.
I used these steps to get back on track:
1) systemctl stop php5-fpm
2) mv /var/www/owncloud /var/www/owncloud-backup-2016-04-09)
3) apt-get install --reinstall owncloud owncloud-files
4) cp -P /var/www/owncloud-backup-2016-04-09/config/config.php /var/www/owncloud/config
5) Log in as admin and disable/reenable extensions to "re-activate" them.
I also moved over some other custom files such as themes.
Thanks for the timely help, and sorry for the noise on what appears to have been my oversight.
Steps to reproduce
Expected behaviour
Integrity check should pass.... or even show any sha512sum.
Actual behaviour
All files fail the integrity check and output a blank sha512sum.
Server configuration
Operating system: Debian 8.4
Web server: nginx 1.9.10-1~bpo8+1
Database: mariadb 10.0.23-0+deb8u1
PHP version: 5.6.19+dfsg-0+deb8u1 (php5-fpm)
ownCloud version: 9.0.1
Updated from an older ownCloud or fresh install: upgrade
Where did you install ownCloud from: owncloud.org's build repos
Signing status (ownCloud 9.0 and above):
List of activated apps:
The content of config/config.php:
Are you using external storage, if yes which one: no
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Firefox
Operating system: Archlinux
Logs
Web server error log
ownCloud log (data/owncloud.log)
Browser log