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 generally both CODE and OnlyOffice do not store anything persistently on the app itself. So given that you tried installing a fresh OnlyOffice instance altogether (uninstall+install) this issue might be more likely to be Nextcloud and their OnlyOffice connector related. So maybe look there for more info.

@girish said in Cloudron update failing:

Indeed, the docker install logic was not cleaned up properly when we cleaned up other package installs. fixed now - https://git.cloudron.io/cloudron/box/-/commit/09d3d258b61ba338c0fadc88c0418d8bcc77f528 . Thanks for investigating!

Perhaps that fixes a similar bug, but just for clarity, note that I was using an old version Cloudron (6.1.2), and got stuck in this other loop that looks like it has already been removed from the script between version 6.2 and 6.3.

while ! dpkg --force-confold --configure -a; do log "Failed to fix packages. Retry" sleep 1 done

That “Failed to fix packages” is the message that appeared again and again in my infinite logs:

2022-01-13T17:05:53 ==> installer: Updating from 6.1.2 to 6.2.7 2022-01-13T17:05:53 ==> installer: updating docker 2022-01-13T17:05:58 ==> installer: Waiting for all dpkg tasks to finish... dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-modules-extra-5.4.0-59-generic; however: Package linux-modules-extra-5.4.0-59-generic is not installed. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 5.4.0.59.62); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-5.4.0-59-generic: linux-image-5.4.0-59-generic depends on linux-modules-5.4.0-59-generic; however: Package linux-modules-5.4.0-59-generic is not installed. dpkg: error processing package linux-image-5.4.0-59-generic (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-generic linux-generic linux-image-5.4.0-59-generic 2022-01-13T17:05:58 ==> installer: Failed to fix packages. Retry dpkg: dependency problems prevent configuration of linux-image-generic: … …

@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:
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.

@girish That did the trick. Thanks!

@imc67 said in Updating FreeScout failed:

@girish said in Updating FreeScout failed:

@imc67 there is a bug here . Can you apply this one liner and then set the memory limit https://git.cloudron.io/cloudron/box/-/commit/750f313c6a36d8d961892df4a41cb7c41faa1f1b ? You have systemctl restart box after you change that line in /home/yellowtent/box/src/apps.js.

Will try this in a few hours

@girish this solved the bug, thanks!

@drpaneas Just give that redis more memory. The "e1ca318a" is the app id. If you put in the search in the apps view, you will know which app's redis needs a bit more memory. It was reported earlier that pixelfed's redis needs more memory after the update. I guess this is because of update to Redis 5.

@johnbolt You should try a forced refresh (ctrl + shift + R on most browsers), to avoid cache issues

@girish ah so that’s because I was messing with dind for GitLab runner... whoops. Thanks for taking a look!

@imc67 I made https://git.cloudron.io/cloudron/box/-/issues/717 for keeping mail backups separately from the box backups.

@valkalon Cloudron support is still the best 😉

Solution :
In my case, /home/yellowtent was owned by root, gpg was trying to create "~/.gpg".
My fix : "chown yellowtent:yellowtent /home/yellowtent/"

There we go, it is updating now. Thanks so much.

Right, we don't recommend upgrading since we trying to keep our testing simple. Security updates are enabled for the base packages that we use. We don't really use many base packages - nginx, collectd. Rest are all containerized (mysql/mongo/redis/email etc) and updated via our docker updates. Docker, nodejs itself are all installed from binaries and not via apt.

Good point, I thought this would be triggered by the security update job from ubuntu already, but apparently not.

Thanks all!

I just installed it on 1 of my Cloudron servers (at DO) to see and experience if and how it works.

@girish All these years and it’s still a pain >_<

Edit: I’m referring to Linux distros ofc, not Cloudron. 🙃

The app does some reason in unresponsive on first start after an update. I had to restart the app after the app and it starts up fine.

For the next update, I will see if this happens again. If that's the case, I will fix up the package to restart the app. I couldn't find anything in the release notes