Cloudron on 18.04.5 - GLIBC_2.28 not found (required by node)
-
Partnerwrote on Jun 28, 2023, 8:02 AM last edited by girish Jun 28, 2023, 9:46 AM
Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: box.service: Main process exited, code=exited, status=1/FAILURE Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: box.service: Failed with result 'exit-code'. Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: box.service: Service hold-off time over, scheduling restart. Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: box.service: Scheduled restart job, restart counter is at 166209. Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: Stopped Cloudron Admin. Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: Started Cloudron Admin. Jun 28 08:01:11 ubuntu-2gb-fsn1-2 box.js[24427]: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
Incident logging topic.
-
Looks like Ubuntu 18.04.05 is the issue.
Attempting upgrade to 20.04 to fix the Issue.Upgrade to Ubuntu 20.04 solved the Issue.
-
Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: box.service: Main process exited, code=exited, status=1/FAILURE Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: box.service: Failed with result 'exit-code'. Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: box.service: Service hold-off time over, scheduling restart. Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: box.service: Scheduled restart job, restart counter is at 166209. Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: Stopped Cloudron Admin. Jun 28 08:01:10 ubuntu-2gb-fsn1-2 systemd[1]: Started Cloudron Admin. Jun 28 08:01:11 ubuntu-2gb-fsn1-2 box.js[24427]: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
Incident logging topic.
Partnerwrote on Jun 28, 2023, 8:04 AM last edited by BrutalBirdie Jun 28, 2023, 8:05 AMLooks like Ubuntu 18.04.05 is the issue.
Attempting upgrade to 20.04 to fix the Issue. -
Looks like Ubuntu 18.04.05 is the issue.
Attempting upgrade to 20.04 to fix the Issue.Upgrade to Ubuntu 20.04 solved the Issue.
-
-
-
Yes this is the reason why we stopped supporting Ubuntu 18
See also https://forum.cloudron.io/post/68921
-
Yes this is the reason why we stopped supporting Ubuntu 18
See also https://forum.cloudron.io/post/68921
@nebulon happend on a server with Cloudron version v7.4.2 tho
-
wrote on Jul 8, 2023, 7:28 PM last edited by
I am facing the same Problem.
Do I have to be careful with something, when upgrading to Ubuntu 20.04?
I'm told at the ssh-login not to upgrade the System via console. Thats why I'm asking. -
@Cetheus We have a guide at https://docs.cloudron.io/guides/upgrade-ubuntu-20/ to upgrade ubuntu. It's fine to upgrade all packages (for ubuntu 18 to 20).
-
wrote on Jul 9, 2023, 2:51 PM last edited by
just be careful about to boot partition, that fucked up my update from 18 to 20 and i had to reinstall everything, make sure you have backups for your cloudron stuff!
-
just be careful about to boot partition, that fucked up my update from 18 to 20 and i had to reinstall everything, make sure you have backups for your cloudron stuff!
wrote on Jul 9, 2023, 4:59 PM last edited by@RazielKanos Thanks for the warning.
I'm running a Mastodon Instance.
Then I will take a look how to back it up via command line. -
wrote on Jul 13, 2023, 7:04 PM last edited by
Thanks for all your help.
The Server is up and running again -
Also for others to come here, to get back up on Ubuntu 18.04 run the following commands via SSH:
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
Then the system should be working again, however for the 7.5 update ubuntu has to be upgraded first.
-
-