Cloudron Forum

@jdaviescoates said in How to cancel an update?: @vladimir-d said in How to cancel an update?: FTR, "Retry update task" and then "Restart App" have sorted the issue. And then revert to previous backup? @jdaviescoates It would be yes if there was a recent backup copy.

@eddowding said in Updating Cloudron to a stable version: I was migrating servers when I noticed that I'm on 7.2.5, but the latest is 7.3.2. When moving to the new server, you can install it as ./cloudron-setup --version 7.2.5 . 7.3 was out last week, just ironing out some regressions. We expect to start rolling it out next week.

Also, the reason for nextcloud update is that it has some slightly tricky optimization to change ownership of files carefully. It also changes the default data directory of newer nextcloud installations.

@robi said in Best way to update from Ubuntu 18.04 to 20.04?: one can use the -y option for apt to 'assume yes' to all prompts. this doesn't work with do-release-upgrade for whatever reason.

@jdaviescoates Oh, it was made available to all only yesterday. So, probably takes a couple more days to actually auto-update.

As a hack, change the update schedule for every hour Related note: would be nice if we could display "the app is xx updates behind". We don't have an appstore API for this though.

@JOduMonT it is only a daemon, but sometimes containers are recreated, images are managed and so forth which may use up a lot of server resources temporarily, especially if disk I/O is slow. To give some reference here, we are talking about the code section from https://git.cloudron.io/cloudron/box/-/blob/master/src/apptask.js#L318 to https://git.cloudron.io/cloudron/box/-/blob/master/src/apptask.js#L340 so something is slow on your system in that area. Not sure how much tinkering you want to do for debugging, but you could stray in some console.log()s there to narrow down the issue. I can also help here, if you enable remote SSH support and send us a mail with your dashboard domain to support@cloudron.io

This happened to me to, and I had to do a full reboot to get the apps back up.

@Gary-Host Thanks. So to be clearer here about the update logs. First, tail the log file /home/yellowtent/platformdata/logs/box.log Now, start the update in the UI You will see something like this in the logs: 2022-03-17T05:30:00.012Z box:tasks startTask - starting task 3970 with options {}. logs at /home/yellowtent/platformdata/logs/tasks/3970.log 2022-03-17T05:30:00.012Z box:shell startTask spawn: /usr/bin/sudo -S -E /home/yellowtent/box/src/scripts/starttask.sh 3970 /home/yellowtent/platformdata/logs/tasks/3970.log 0 400 Now, you can check the log file as listed above at /home/yellowtent/platformdata/logs/tasks/3970.log That should give us info on why it's not updating.

@humptydumpty said in Backup Failed: This is most likely to do with postgresql not having enough memory. Please go to Services and bump up the postgres memory.

@scooke I am now having an issue with my Onlyoffice app Not responding Fails to update Logs show this every few minutes Oct 21 17:30:59 => Initialize database Oct 21 17:30:59 psql: error: connection to server at "postgresql" (fd00:c107:d509::80), port 5432 failed: Connection refused Oct 21 17:30:59 Is the server running on that host and accepting TCP/IP connections? Oct 21 17:30:59 connection to server at "postgresql" (172.18.0.34), port 5432 failed: Connection refused Oct 21 17:30:59 Is the server running on that host and accepting TCP/IP connections? Any thoughts ? EDIT : I checked Services and saw Redis for this app had stopped. Restarted w/o problem. But postgresql is shown in orange status and is trying to restart constantly. Those logs show : Oct 21 17:38:05 Debug mode. Sleeping Oct 21 17:38:20 Detected existing installation Oct 21 17:38:20 Resetting root password Oct 21 17:39:21 Detected existing installation Oct 21 17:39:21 Resetting root password Oct 21 17:40:23 Detected existing installation Oct 21 17:40:23 Resetting root password EDIT(2) : rebooted box, postgresql restarted, seems to have cleared the issue.

To close the thread here, the issue was simply that update to 7.5 was failing because @squareclouds 's cloudron is still on ubuntu 18 . One must upgade to Ubuntu 20 first before updating to 7.5.

@girish Seemed like maybe Ubuntu was finishing some updates on boot which was blocking ssh from starting. I was pinging on 80 and 443 ports but ssh wasn't responding on 22 or 202 for a while.

@girish I found this when i clicked update: [image: 1639218382101-61f3d999-30ce-405d-9639-1e1c26465759-image.png] Both my apps are running and are accessible. I now tried stopping the Nextcloud instance and started it. And it the app the 1 dead app is now 2 alive and 0 dead. Now i could update normally. Not sure what i missed in the first place but now works. Thanks for the help

I have added a retry now for the startup tasks on db failures in 7.0.2

@girish @nebulon I did not follow the upgrade tutorial for 16.04 → 18.04 → 20.04 entirely because I have some minor adjustments on the server that were blocking the upgrade. Also, there was a minor issue with docker in the past, where I edited the file /etc/apt/sources.list.d/docker.list so this whole problem was my fault

@privsec That worked, thanks!

@girish I would avoid deleting them, but instead migrate them to the deactivated directory.

@d19dotca Also, it's probably not clear from the UI because the UI is not optimized for the early upgraders. You can see https://git.cloudron.io/cloudron/box/-/blob/master/CHANGES for what exactly is the fix in the patch release.

Generally, I am wary of putting this information for general use (and even in docs) because many things can go wrong . So, please, if you care about the data, don't hesitate to contact us on support@ . We help regardless of the subscription plan.