Cloudron 5.2 update failed
I logged into cloudron this morning, and all the sudden, it kept giving me Nginx 500 Errors.
Later I updated to the latest release of this week.
The errors continued.
Then I've realized that redis is missing from the system?!
Anyone able to help me out? This is a production server and we urgently need this fixed.
@Trankery Can you check the server logs? The file
/home/yellowtent/platformdata/logs/box.loghas the logs. Do you see any errors?
So there was a crash because of redis:
invalid argument "NaN" for "-m, --memory" flag: invalid size: 'NaN' See 'docker run --help'. at ChildProcess.exithandler (child_process.js:294:12) at ChildProcess.emit (events.js:198:13) at maybeClose (internal/child_process.js:982:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) killed: false, code: 125, signal: null, cmd:
There is a bug that if the redis memory limit is adjusted before the platform code starts up, it crashes. This is because of a typo in the code
In the rare chance someone else hits this, just apply the one line change to
/home/yellowtent/box/src/addons.js- https://git.cloudron.io/cloudron/box/-/commit/4ede765e1f9a1a89d497255465721b0b930db642 and then
systemctl restart box.
@girish No Idea how this happened! Sorry!
My whole cloudron was not really working after the update. I did a reboot, nothing really changed, System looked like this:
After the fix from @girish and restart of box everything worked again.
Hope you push a hotfix pretty soon for all others. Still wish for a GUI option to choose if i want auto or manually install system updates, just for cases like this (this exists for the apps and has existed for the cloudron itself in the past). Auto updates always have this bitter aftertaste of waking up next day and it could work or not work.
valkalon last edited by
Same here thanks for the fix @girish it worked! I got to say I was scared, glad you reacted so fast
@valkalon Cloudron support is still the best