Cloudron not reachable after reboot
-
Hi all,
I rebooted my Cloudron instance after noticing a series of failed backups. Now no apps are responding, nor is the main dashboard.
I tried killing all the docker containers and doing a manual start via
/home/yellowtent/box/setup/start.sh
, but no luck. Here is the output fromstart.sh
:root@my:~# /home/yellowtent/box/setup/start.sh 2023-07-13T19:54:19 ==> start: Cloudron Start media:x:500: 2023-07-13T19:54:19 ==> start: Configuring docker Synchronizing state of apparmor.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable apparmor 2023-07-13T19:54:20 ==> start: Ensuring directories 2023-07-13T19:54:20 ==> start: Configuring journald 2023-07-13T19:54:20 ==> start: Setting up unbound 2023-07-13T19:54:20 ==> start: Adding systemd services Synchronizing state of unbound.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable unbound Synchronizing state of cron.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable cron 2023-07-13T19:54:22 ==> start: Configuring sudoers 2023-07-13T19:54:22 ==> start: Configuring collectd 2023-07-13T19:54:22 ==> start: Configuring sysctl 2023-07-13T19:54:22 ==> start: Configuring logrotate 2023-07-13T19:54:22 ==> start: Adding motd message for admins 2023-07-13T19:54:22 ==> start: Configuring nginx 2023-07-13T19:54:22 ==> start: Starting mysql mysqladmin: [Warning] Using a password on the command line interface can be insecure. Warning: Since password will be sent to server in plain text, use ssl connection to ensure password safety. mysql: [Warning] Using a password on the command line interface can be insecure. 2023-07-13T19:54:22 ==> start: Migrating data node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
Host info:
Linux my.domain.io 6.2.9-x86_64-linode160 #1 SMP PREEMPT_DYNAMIC Wed Apr 5 15:30:32 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux
And the last few lines of output from
/home/yellowtent/platformdata/logs/box.log:
box-task-11853.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11853 /home/yellowtent/platformdata/logs/0056c5e5-9e1d-49ac-946a-e8a18cd9b656/apptask.log box-task-11854.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11854 /home/yellowtent/platformdata/logs/d849454e-eeb8-4fdb-93f2-146b75b220e2/apptask.log box-task-11855.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11855 /home/yellowtent/platformdata/logs/tasks/11855.log box-task-11856.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11856 /home/yellowtent/platformdata/logs/tasks/11856.log box-task-11857.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11857 /home/yellowtent/platformdata/logs/tasks/11857.log box-task-11858.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11858 /home/yellowtent/platformdata/logs/tasks/11858.log box-task-11859.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11859 /home/yellowtent/platformdata/logs/tasks/11859.log box-task-11860.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11860 /home/yellowtent/platformdata/logs/tasks/11860.log box-task-11861.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11861 /home/yellowtent/platformdata/logs/tasks/11861.log box-task-11862.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11862 /home/yellowtent/platformdata/logs/0056c5e5-9e1d-49ac-946a-e8a18cd9b656/apptask.log box-task-11863.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 11863 /home/yellowtent/platformdata/logs/d849454e-eeb8-4fdb-93f2-146b75b220e2/apptask.log 2023-07-13T14:40:00.982Z box:shell stopTask (stdout): All tasks stopped 2023-07-13T14:40:01.014Z box:scheduler could not run task housekeeping : Expected "actual" to be strictly unequal to: null
Thanks! I've been using Cloudron for many years now and had almost no problems, and any I have had have always been promptly resolved by the great support you guys do.
-
@ssklash This happens because of update Cloudron 7.5 + Ubuntu 18.04. If you upgrade ubuntu to Ubuntu 20.04, it will work again. Please reach out on support@cloudron.io if you hit any issues with that. https://docs.cloudron.io/guides/upgrade-ubuntu-20/ is the guide
-
Check the contents of
/home/yellowtent/box/VERSION
. Is it 7.4.3 ? If so, you can run the commands below and make it work again . After you get it back, snapshot the server and upgrade ubuntu when possible.mkdir -p /usr/local/node-16.18.1 curl -sL https://nodejs.org/dist/v16.18.1/node-v16.18.1-linux-x64.tar.gz -o /tmp/node.tar.gz tar zxvf /tmp/node.tar.gz --strip-components=1 -C /usr/local/node-16.18.1 rm /tmp/node.tar.gz ln -sf /usr/local/node-16.18.1/bin/node /usr/bin/node ln -sf /usr/local/node-16.18.1/bin/npm /usr/bin/npm systemctl restart box