No automatic app updates with pending box update?

[nebulon]

Unless there is a bug, those two update mechanisms are not really connected that way. Is there any indication in the logs, that maybe the updater job got stuck?

[fbartels]

Hi @nebulon,

I went through the box.log and only found entries like this:

2023-12-20T02:00:00.095Z box:cron Starting box autoupdate to {"version":"7.6.1","changelog":["api: return json when route not found","app proxy: Host header is set to match the proxy domain instead of the target domain","dyndns: update dns every 10 mins","mail: add option to enable/disable Virtual All mailbox","New base image 4.2.0. `cloudron/base:4.2.0@sha256:46da2fffb36353ef714f97ae8e962bd2c212ca091108d768ba473078319a47f4`","notifications: Add color coded indicator to notifications","oidc: add oidc logo as login indicator for apps","oidc: fix issue with redirects not working on iOS apps","oidc: loginRedirectUri can be empty string","turn: add ddos mitigation settings","Update MongoDB to 5.0. Important: this release requires AVX support in CPU","volumes: edit options for network mounts"],"sourceTarballUrl":"https://releases.cloudron.io/box-1122137d12-1122137d12-7.6.1.tar.gz","sourceTarballSigUrl":"https://releases.cloudron.io/box-1122137d12-1122137d12-7.6.1.tar.gz.sig","boxVersionsUrl":"https://releases.cloudron.io/versions.json","boxVersionsSigUrl":"https://releases.cloudron.io/versions.json.sig","unstable":false}
2023-12-20T02:00:00.163Z box:cron Failed to box autoupdate: 7.6.1 requires AVX support

and

2023-12-20T05:16:50.272Z box:apphealthmonitor app health: 22 running / 1 stopped / 0 unresponsive
2023-12-20T05:17:00.008Z box:updatechecker checkBoxUpdates: checking for updates
2023-12-20T05:17:00.343Z box:apphealthmonitor app health: 22 running / 1 stopped / 0 unresponsive
2023-12-20T05:17:03.081Z box:updatechecker checkAppUpdates: checking for updates
2023-12-20T05:17:03.081Z box:updatechecker checkBoxUpdates: Skipping notification of box update 7.6.1 as user was already notified
2023-12-20T05:17:10.286Z box:apphealthmonitor app health: 22 running / 1 stopped / 0 unresponsive

This is while there is currently a vikunja update pending.

[nebulon]

Taking a closer look a the code path, indeed if there is a Cloudron update it will first attempt to run that and then will wait for the next cron updater to handle the apps once there is no Cloudron update pending: https://git.cloudron.io/cloudron/box/-/blob/master/src/cron.js?ref_type=heads#L219

Of course in your case it will always be pending. Will fix for next release.

[fbartels]

Thank you. I am assuming the next release will be a 7.6.x however, or not?

Just checked again the run time of the current server and its still under contract till april, so I will get to planning the migration sometime in q1 next year.

[nebulon]

That is true, the fix will not really reach your server with such a release. I guess you would have to patch that file then. Will link the patch here then once done.

[fbartels]

Much appreciated

[nebulon]

Since this may take a bit to get done with proper testing, you may just skip the return at https://git.cloudron.io/cloudron/box/-/blob/master/src/cron.js?ref_type=heads#L223 for the moment to get over the issue. Have to discuss back with @girish more on the potential side-effects first.

[girish]

I have made a fix with https://git.cloudron.io/cloudron/box/-/commit/fa842034edfc0b8ba65a2c339a9b28112471945f . @fbartels unfortunately, you have to apply that patch manually on your server.

[fbartels]

Hi @girish,

thanks for the patch. I have just applied it manually and restarted the box service afterwards. There are currently some updates pending, so I will be able to report back tomorrow if these updates have been applied.

[fbartels]

Just a small confirmation from my side that app updates were now automatically applied. Case closed.

[eddowding]

@girish amazing, thank you!

Can you provide a Dummy's Guide to How to Use this Patch, please?

[girish]

@eddowding you have to modify the file /home/yellowtent/box/src/cron.js and the systemctl restart box.

If you are not comfortable making the changes, you can write to us at support@cloudron.io and we can apply the changes for you.