Solved Updating from v7.1.4

[cpa]

Hi there,

I'm running cloudron v7.1.4 and would like to upgrade to the latest version (my instance believes it is v7.2.2). Unfortunately, the update fails with:

{
  "taskId": "8358",
  "errorMessage": "Failed to download https://s3.amazonaws.com/prod-cloudron-releases/versions.json: downloadUrl exited with code 22 signal null",
  "timedOut": false
}

The URL in the message indeed 403's, so either the resource should be available and I just have to wait for it to be available again or I'll have to change something on my end.

Any advice?

[girish]

@cpa We moved out of AWS a while ago. Looks like older version of Cloudron is caching the old release. To fix:

• Delete the file /home/yellowtent/platformdata/update/updatechecker.json
• systemctl restart box
• Now , Settings -> Check for updates and then try to update

[cpa]

Thanks, but the update fails with another error now:

Jan 14 20:43:38 box:tasks startTask - starting task 8390 with options {"timeout":72000000,"nice":15,"memoryLimit":800}. logs at /home/yellowtent/platformdata/logs/tasks/8390.log
Jan 14 20:43:38 box:shell startTask spawn: /usr/bin/sudo -S -E /home/yellowtent/box/src/scripts/starttask.sh 8390 /home/yellowtent/platformdata/logs/tasks/8390.log 15 800
Jan 14 20:43:38 box:shell startTask (stdout): Running as unit: box-task-8390.service
Jan 14 20:43:39 box:shell startTask (stdout): 12004 (process group ID) old priority 0, new priority 15
Jan 14 20:43:40 box:apphealthmonitor app health: 1 alive / 0 dead.
Jan 14 20:43:50 box:apphealthmonitor app health: 1 alive / 0 dead.
Jan 14 20:43:53 box:cloudron Getting logs for box as json
Jan 14 20:44:00 box:apphealthmonitor app health: 1 alive / 0 dead.
Jan 14 20:44:10 box:apphealthmonitor app health: 1 alive / 0 dead.
Jan 14 20:44:20 box:apphealthmonitor app health: 1 alive / 0 dead.
Jan 14 20:44:22 box:shell startTask (stdout): Finished with result: exit-code
processes terminated with: code=exited/status=50
runtime: 44.317s
Jan 14 20:44:22 box:shell startTask code: 50, signal: null
Jan 14 20:44:22 box:tasks startTask: 8390 completed with code 50 and signal null
Jan 14 20:44:22 box:locker Released : box_update
Jan 14 20:44:22 box:updater Update failed with error {
stack: 'BoxError: update exited with code 1 signal null\n' +
' at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:78:17)\n' +
' at ChildProcess.emit (node:events:390:28)\n' +
' at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)',
name: 'BoxError',
reason: 'Spawn Error',
details: {},
message: 'update exited with code 1 signal null',
code: 1,
signal: null
Jan 14 20:44:22 box:tasks startTask: 8390 done. error: [object Object]
Jan 14 20:44:30 box:apphealthmonitor app health: 1 alive / 0 dead.

[girish]

@cpa most likely this seems to be an issue with apt not working properly/stuck with some update. Can you check if dpkg --configure -a works on the server?

[cpa]

It indeed fails with:

dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-modules-extra-4.15.0-176-generic; however:
  Package linux-modules-extra-4.15.0-176-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 (= 4.15.0.176.165); however:
  Package linux-image-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-generic
 linux-generic

What should I do, since the MOTD notes Please do not run apt upgrade manually as it will update packages that Cloudron relies on and may break your installation. Ubuntu security updates are automatically installed on this server every night. ?

[girish]

@cpa looks like some kernel update is not going through. Can you try updating manually ?

I think apt-get -f install or apt-get install linux-image-generic. In fact, just go ahead and run any apt command required to get over the error.

[cpa]

So I've googled the error and ran apt --fix-broken install. I think it broke because I had ran out of space a while ago.

Anyway, I was able to update to v7.2.2 and then to v7.2.5 (but it did not offer to upgrade to v7.2.5 directly).

Everything looks good now, thanks!

[girish]

@cpa ah, thanks. Another command for me to remember when troubleshooting apt...

[gerben]

For statistics, had the same issue here.

2023-02-08T13:57:54.944Z box:tasks setCompleted - 6496: {"result":null,"error":{"stack":"BoxError: Failed to download https://s3.amazonaws.com/prod-cloudron-releases/versions.json: downloadUrl exited with code 22 signal null\n    at /home/yellowtent/box/src/updater.js:50:26\n    at processTicksAndRejections (internal/process/task_queues.js:95:5)\n    at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20)\n    at async downloadUrl (/home/yellowtent/box/src/updater.js:42:5)\n    at async downloadAndVerifyRelease (/home/yellowtent/box/src/updater.js:110:5)\n    at async update (/home/yellowtent/box/src/updater.js:145:25)","name":"BoxError","reason":"Network Error","details":{},"message":"Failed to download https://s3.amazonaws.com/prod-cloudron-releases/versions.json: downloadUrl exited with code 22 signal null"}}

I deleted /home/yellowtent/platformdata/update/updatechecker.json, and also versions.json.sig from the same folder (otherwise there was no ‘check versions’ button at all in the UI). Then systemctl restart box as described, seemed to work. (to then discover other update issues, but probably unrelated..)

[zypA13510]

@girish said in Updating from v7.1.4:

@cpa We moved out of AWS a while ago. Looks like older version of Cloudron is caching the old release. To fix:

• Delete the file /home/yellowtent/platformdata/update/updatechecker.json
• systemctl restart box
• Now , Settings -> Check for updates and then try to update

Facing the same issue here, and this resolved it for me.

And now I realized that my installation was multiple versions behind (like at least half-a-year behind), despite having weekly auto-update enabled. I'm afraid there could be more people like me who didn't check and didn't know it is stuck on 7.1.4.