Nextcloud failed on upgrade and does not start after Turris OS 3.11.5 upgrade

Software SW bugs discussion
1

Hi everyone,

it seems that Nextcloud shipped with Turris OS 3.11.5 does not start after upgrade. Web interface says “Updates between multiple major versions and downgrades are unsupported.”.

Digging in /var/log/messages revealed a whole lot of error messages like this:

2019-06-19 17:52:10 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/core/doc/admin/genindex.html to /usr/s
hare/updater/collided/srv/www/nextcloud/core/doc/admin
2019-06-19 17:52:10 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/apps/files_trashbin/l10n/ko.json to /u
sr/share/updater/collided/srv/www/nextcloud/apps/files_trashbin/l10n
2019-06-19 17:52:10 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/apps/files_trashbin/l10n/sk.json to /u
sr/share/updater/collided/srv/www/nextcloud/apps/files_trashbin/l10n
2019-06-19 17:52:10 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/settings/l10n/es_CR.js to /usr/share/u
pdater/collided/srv/www/nextcloud/settings/l10n
2019-06-19 17:52:10 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/apps/files_trashbin/l10n/bg.js to /usr
/share/updater/collided/srv/www/nextcloud/apps/files_trashbin/l10n
2019-06-19 17:52:10 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/apps/files_trashbin/l10n/sk.js to /usr
/share/updater/collided/srv/www/nextcloud/apps/files_trashbin/l10n
2019-06-19 17:52:10 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/apps/files_trashbin/l10n/es_PY.js to /
usr/share/updater/collided/srv/www/nextcloud/apps/files_trashbin/l10n
2019-06-19 17:52:11 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/settings/l10n/da.js to /usr/share/upda
ter/collided/srv/www/nextcloud/settings/l10n
2019-06-19 17:52:11 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/settings/l10n/is.js to /usr/share/upda
ter/collided/srv/www/nextcloud/settings/l10n
2019-06-19 17:52:11 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/apps/dav/l10n/sr.json to /usr/share/up
dater/collided/srv/www/nextcloud/apps/dav/l10n
2019-06-19 17:52:11 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/apps/dav/l10n/sv.json to /usr/share/up
dater/collided/srv/www/nextcloud/apps/dav/l10n
2019-06-19 17:52:11 warning updater[25211]: backend.lua:801 (user_path_move): Collision with existing path. Moving /srv/www/nextcloud/settings/l10n/sv.js to /usr/share/upda
ter/collided/srv/www/nextcloud/settings/l10n

and it continues on and on.

Complete log from update is here: https://spackovi.net/petr/a/2019/06/19-messages.bz2

Nextcloud was installed from packages year ago and never modified by hand.

Could you recommend a way to fix this installation?

Thank you!
Petr Špaček

2

Im guessing here, but try to force extract one major version above what you had, visit the website, complete the upgrade, and so on, until you’re with the current version

3

I can confirm the issue. :slightly_frowning_face:

Screenshot%20from%202019-06-21%2009-26-47_nextcloud_update_failed
Screenshot%20from%202019-06-21%2009-26-47_nextcloud_update_failed365×545 63 KB

While used my nextcloud the other day I’m pretty sure the malfunction came with the update to Turris OS 3.11.5.
So how can we recover from the issue in a clean and simple way?

4

I need to say that this is not our fault. Yesterday, colleagues were able to help @pspacek and they reached the conclusion as the Nextcloud must be on external storage.

What most probably happened is that during the update from version 14 to version 15, the external disk was not mounted, so the Nextcloud was updated on the internal storage. However, once the external disk was mounted back, there was still Nextcloud 14 and from that version, it was updated to Nextcloud 16, so it skipped the version 15, which is not recommended.

1 Like
5

Yes, that’s most likely cause in my case.

I’ve fixed that by manually downgrading to
https://repo.turris.cz/archive/omnia/3.11.4/packages/turrispackages/nextcloud_15.0.5-0_mvebu.ipk
https://repo.turris.cz/archive/omnia/3.11.4/packages/turrispackages/nextcloud-install_15.0.5-0_mvebu.ipk

and then upgrading to latest version. Use wget to download packages and opkg install --force-downgrade <package> to force downgrade. Then upgrade - it worked for me after that.

It would be good if updater had ability to detect disconnected external storage, because upgrading half of the system is going to cause trouble … But that’s improvement for another day.

2 Likes
6

Just for the sake of completeness: You did call the Webpage of your Nextcloud after downgrading to 15.0.5.0, didn’t you?

7

Sorry, I do not understand what you mean by “call the web page”. I do not remember if upgrade script was triggered by package downgrade or if I did occ upgrade manually, sorry about that.

8

Sorry for my unclear statement. After some homework with my TO I can say in fact I meant sudo -u nobody php-cli occ upgrade.

Because of the failed “occ upgrade” in my case I did a fresh installation of version 16.0.x.y and applied my backup files and folders according to official Nextcloud backup restore manual.
I needed to do an additional “patch” and my Nextcloud works like a charm after that.
Thank a lot to you all!

kind regards
Chris

9

Really? Don’t you recommend in the official documentation to install it on external storage? You should know better!

To cite the documentation:

excessive writing to the internal memory will lead to it getting worn out and damaged soon

I guess you will offer exchange of the internal memory for free then, when you are damaging it for the users, right?