Nextcloud upgrade failed
-
Oddly, my Nextcloud shows this in the logs while the app is not responding:
[no timestamp] Update failed","userAgent":"--","version":"25.0.2.3","data":{"app":"updater"}} [no timestamp] upgrade from 25.0.2.3 to 29.0.2.2","userAgent":"--","version":"25.0.2.3","data":{"app":"core"}} [no timestamp] Maintenance mode is kept active","userAgent":"--","version":"25.0.2.3","data":{"app":"updater"}} [no timestamp] Reset log level to Error(3)","userAgent":"--","version":"25.0.2.3","data":{"app":"updater"}}This is odd, because I have done updates regularly all the time. But I am not sure how to resolve this.
Since all the data Nextcloud uses is on a mounted block storage, I was wondering if I can simply set up Nextcloud again but use the same data directory, then I can remove this instance and change the domain.
Not sure if there is a better course of action, or if I did this, how can I get another Nextcloud instance to use this data directory?
-
upgrade from 25.0.2.3 to 29.0.2.2
@ekevu123 are you trying to update nextcloud from inside nextcloud ? somehow the above line doesn't make sense. Cloudron packages are shipped for every patch version, so this is a bit hard to understand.
-
No, I haven't tried anything like that. We discussed in another thread how I tried to resize my Vultr Block storage, which I now successfully have done. I haven't changed anything else, so I am as surprised as you are about this error.
But how do we solve it? I wouldn't mind setting up a fresh Nextcloud if I could connect all my block storage data to it.
-
@ekevu123 said in Nextcloud upgrade failed:
But how do we solve it? I wouldn't mind setting up a fresh Nextcloud if I could connect all my block storage data to it.
Did you mount the block storage inside Nextcloud or via Cloudron Volume ? i.e you added a Cloudron Volume and then used the https://docs.cloudron.io/apps/#data-directory feature ?
If you have the files locally, can't you set up a new nextcloud, move data directory and then sync up all the files again ?
-
I do have the files locally and I could set everything up again, but I was trying to avoid that process. But if there is no other way, then sure.
I used the volume as the main data directory for the app, not as an external storage within Nextcloud. The volume is fully accessible, all files are there as well, and I have set up a second Nextcloud instance for testing, but I cannot get it to use the configuration and files of the other.
-
Nextcloud maintains the file listing in its Postgres database, so whatever is on disk will not automatically picked up by it. If data on disk is changed behind its back, all sorts of issues will arise with Nextcloud.
If you are confident enough about the directory structure on disk, you could attempt to make Nextcloud rescan all files: https://docs.cloudron.io/apps/nextcloud/#rescan-files -
I appreciate the advice, but I am not confident that this would solve the problem completely. So, I am going to use a fresh install and upload all data again.
Perhaps something went very wrong while running out of disk space plus resizing the block storage with having the whole Nextcloud installation on the volume, not just its data. -
... but it seems like uninstalling this Nextcloud instance is not as easy as I had thought: I am stuck at tearing down addons and the app froze in the process, the logs don't show anything.
Is there a way to force the uninstall? I suppose the problem is somehow related to the fact that the installation is on the block storage itself, but if there is a problem accessing it for some reason, we cannot uninstall the app properly either.
-
From the logs, this was 10 minutes ago:
Jun 26 15:07:08
Jun 26 15:07:08 Command "upgrade" is not defined.
Jun 26 15:07:08 ==> run migration
Jun 26 15:07:08 ==> update config
Jun 26 15:07:08 Nextcloud is not installed - only a limited number of commands are available
Jun 26 15:07:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Jun 26 15:07:27 => Healtheck error: Error: Timeout of 7000ms exceeded
Jun 26 15:07:37 => Healtheck error: Error: Timeout of 7000ms exceeded
Jun 26 15:07:47 => Healtheck error: Error: Timeout of 7000ms exceeded
Jun 26 15:07:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.17.60:80
Jun 26 15:08:01 box:taskworker Starting task 4625. Logs are at /home/yellowtent/platformdata/logs/c7c7e8c7-4120-4f85-bdaa-c05453fac2ed/apptask.log
Jun 26 15:08:01 box:apptask run: startTask installationState: pending_uninstall runState: running
Jun 26 15:08:01 box:tasks update 4625: {"percent":20,"message":"Deleting container"}
Jun 26 15:08:01 box:shell reload /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
Jun 26 15:08:02 box:apptask deleteContainer: deleting app containers (app, scheduler)
Jun 26 15:08:02 box:shell removeLogrotateConfig /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurelogrotate.sh remove c7c7e8c7-4120-4f85-bdaa-c05453fac2ed
Jun 26 15:08:02 box:tasks update 4625: {"percent":30,"message":"Teardown addons"}
Jun 26 15:08:02 box:services teardownAddons: Tearing down ["postgresql","sendmail","ldap","redis","localstorage","scheduler","turn"]
Jun 26 15:08:02 box:services teardownAddons: Tearing down addon postgresql with options {}
Jun 26 15:08:02 box:services Tearing down sendmail
Jun 26 15:08:02 box:services teardownAddons: Tearing down addon sendmail with options {"supportsDisplayName":false}
Jun 26 15:08:02 box:services Tearing down LDAP
Jun 26 15:08:02 box:services teardownAddons: Tearing down addon ldap with options {}
Jun 26 15:08:02 box:services teardownAddons: Tearing down addon redis with options {}
Jun 26 15:08:02 box:shell removeVolume /usr/bin/sudo -S /home/yellowtent/box/src/scripts/rmaddondir.sh redis c7c7e8c7-4120-4f85-bdaa-c05453fac2ed
Jun 26 15:08:02 box:services teardownAddons: Tearing down addon localstorage with options {}
Jun 26 15:08:02 box:services teardownLocalStorage
Jun 26 15:08:02 box:shell clearVolume /usr/bin/sudo -S /home/yellowtent/box/src/scripts/clearvolume.sh rmdir /mnt/next.cloud/next.cloud
Jun 26 15:08:03 => Healtheck error: Error: connect EHOSTUNREACH 172.18.17.60:80
