Upgrade from 7.0.0 to 7.0.1 failed - no logged reason

[StrangeNoises]

Installed from repo on Ubuntu Trusty 64-bit, using Postgresql back-end storage.

After the upgrade installed I visited the site to be prompted to upgrade the database. I told it to start... and it just got stuck there on this page a couple of hours later:

This ownCloud instance is currently being updated, which may take a while.
Please reload this page after a short time to continue using ownCloud.
Contact your system administrator if this message persists or appeared unexpectedly.
Thank you for your patience.

There's nothing logged in data/owncloud.log to do with the upgrade, (the file is timestamped several hours ealier) so I have no idea what's happening. Hopefully you might know where it failed if it failed before even logging that it was starting the upgrade?

The site is completely idle, so I don't think anything is happening. There is a zero-sized data/.ocdata file timestamped to the second time I tried the upgrade, but that's it. Nothing apparently relevant logged in Apache or Postgresql logs either.

The disk is not full (72GB free). The logfile is 45MB, so stuff does get written to it, it is write-enabled for www-data. TBH it could probably do with a logrotate config, but it's fine.

NB: This install was freshly done for Owncloud 6 to use Postgres. The upgrade to Owncloud 7.0.0 happened apparently completely smoothly.

I note the other issue raised here today - #10183 - from someone else having an upgrade failure apparently due to case-sensitivity. I've no idea if this is the same issue, given I didn't get anything in my logfile relating to the upgrade at all.

[StrangeNoises]

Hmm. Found how to turn up the loglevel (set it to 0) and tried again (set maintenance to false again and revisited, and started again)

This time it worked, and completed within seconds and redirected me. All seems fine.

The only thing I did different to my previous attempts was the loglevel change. I literally have no idea what else there was to fiddle with, so didn't.

Nothing at all logged, and it failed, with loglevel to what it was before (2). With loglevel to 0 it worked. FWIW this is what was logged:

{"reqId":"53e13b3312c0b","app":"core","message":"starting upgrade from 7.0.0.8 to 7.0.1.1","level":0,"time":"2014-08-05T20:14:43+00:00","method":"GET","url":"\/owncloud\/core\/ajax\/update.php?requesttoken=228259a465717b812b24"}
{"reqId":"53e13b463fd92","app":"cron","message":"Update required, skipping cron","level":0,"time":"2014-08-05T20:15:02+00:00","method":"--","url":"--"}
{"reqId":"53e13b5ce27ba","app":"core","message":"OC_Image::loadFromFileHandle(): Trying","level":0,"time":"2014-08-05T20:15:24+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2FAvatarMoi-tiny.jpg&c=52ab53bc20285&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5ce27ba","app":"core","message":"OC_Image->fixOrientation() No readable file path set.","level":0,"time":"2014-08-05T20:15:25+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2FAvatarMoi-tiny.jpg&c=52ab53bc20285&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5ce27ba","app":"core","message":"OC_Image->fixOrientation() Orientation: -1","level":0,"time":"2014-08-05T20:15:25+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2FAvatarMoi-tiny.jpg&c=52ab53bc20285&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5d80cac","app":"core","message":"OC_Image::loadFromFileHandle(): Trying","level":0,"time":"2014-08-05T20:15:25+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2FAvatarMoi-tiny.png&c=52ab53bce7269&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5d80cac","app":"core","message":"OC_Image->fixOrientation() No readable file path set.","level":0,"time":"2014-08-05T20:15:25+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2FAvatarMoi-tiny.png&c=52ab53bce7269&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5d80cac","app":"core","message":"OC_Image->fixOrientation() Orientation: -1","level":0,"time":"2014-08-05T20:15:25+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2FAvatarMoi-tiny.png&c=52ab53bce7269&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5e0f671","app":"core","message":"OC_Image::loadFromFileHandle(): Trying","level":0,"time":"2014-08-05T20:15:26+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2FAvatarMoi.png&c=52ab53bdcf434&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5e0f671","app":"core","message":"OC_Image->fixOrientation() No readable file path set.","level":0,"time":"2014-08-05T20:15:26+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2FAvatarMoi.png&c=52ab53bdcf434&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5e0f671","app":"core","message":"OC_Image->fixOrientation() Orientation: -1","level":0,"time":"2014-08-05T20:15:26+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2FAvatarMoi.png&c=52ab53bdcf434&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5e5dfc3","app":"core","message":"OC_Image::loadFromFileHandle(): Trying","level":0,"time":"2014-08-05T20:15:26+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2Fcurrent+issues.txt&c=52ab53caac6ed&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5e5dfc3","app":"core","message":"OC_Image->fixOrientation() No readable file path set.","level":0,"time":"2014-08-05T20:15:26+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2Fcurrent+issues.txt&c=52ab53caac6ed&x=36&y=36&forceIcon=0"}
{"reqId":"53e13b5e5dfc3","app":"core","message":"OC_Image->fixOrientation() Orientation: -1","level":0,"time":"2014-08-05T20:15:26+00:00","method":"GET","url":"\/owncloud\/index.php\/core\/preview.png?file=%2F%2Fcurrent+issues.txt&c=52ab53caac6ed&x=36&y=36&forceIcon=0"}

Actually I think only the first two lines of that relate to the upgrade at all; the rest is just what happened after I logged in.

That's a frustrating one, I guess there's nothing for anyone to look at now. :-} I'll close.

[sm8ps]

Sorry to jump onto a closed report but it fits my case 100%. I had the very same experience while upgrading via the repos for the Ubuntu packages (U12.04, MySQL). No sign of life in 'top' after quite some time.
Feeling brave, changed 'maintenance' to 'false' in 'config.php' and restarted. This time, the upgrade went on as I could verify in 'top'. After half a minute the web-page switched automatically to what looks like a successful upgrade.
However, I do not (want to) know what the database looks like. Anybody have a method for testing?

[DeepDiver1975]

On successful upgrade we reload the page and the user is redirected to the login screen.

All green from my understanding - carry on

[sm8ps]

@DeepDiver1975
Thanks for your reassurance! Any idea why the upgrade got stock at the "please reload this page after a short time"-page? This happened also with the upgrade from 6.0.3 to 7.0.0, cf. #10152. Logs completely harmless, system totally idle.
I am a bit at loss. What would you say, should I file a new bug?