Solved Trouble upgrading from Ubuntu 18.04 to 20.04

[doodlemania2]

Hey yall, I've busted something fun. I followed the instructions https://docs.cloudron.io/guides/upgrade-ubuntu-20/ but getting an issue with node it appears:

Jun 03 14:55:17 apps systemd[1]: Started Cloudron Admin.
Jun 03 14:55:17 apps box.js[202906]: /usr/bin/env: 'node': No such file or directory
Jun 03 14:55:17 apps systemd[1]: box.service: Main process exited, code=exited, status=127/n/a
Jun 03 14:55:17 apps systemd[1]: box.service: Failed with result 'exit-code'.

Workaround be to install node?

[girish]

@doodlemania2 Looks like something removed the symlink.

ln -sf /usr/local/node-16.14.2/bin/node /usr/bin/node
ln -sf /usr/local/node-16.14.2/bin/npm /usr/bin/npm

[doodlemania2]

Now I pay closer attention, that prevented start.sh from succeeding:
root@apps:/etc/apt# /home/yellowtent/box/setup/start.sh
2022-06-03T15:03:03 ==> start: Cloudron Start
media500:
2022-06-03T15:03:03 ==> 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
2022-06-03T15:03:06 ==> start: Ensuring directories
2022-06-03T15:03:06 ==> start: Configuring journald
2022-06-03T15:03:07 ==> start: Setting up unbound
2022-06-03T15:03:07 ==> 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
2022-06-03T15:03:18 ==> start: Configuring sudoers
2022-06-03T15:03:18 ==> start: Configuring collectd
2022-06-03T15:03:18 ==> start: Configuring sysctl
2022-06-03T15:03:18 ==> start: Configuring logrotate
2022-06-03T15:03:18 ==> start: Adding motd message for admins
2022-06-03T15:03:18 ==> start: Configuring nginx
2022-06-03T15:03:19 ==> 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.
mysql: [Warning] Using a password on the command line interface can be insecure.
2022-06-03T15:03:19 ==> start: Migrating data
/usr/bin/env: ‘node’: No such file or directory
2022-06-03T15:03:19 ==> start: DB migration failed

I guess installing node would fix? I do recall looking at the server funny when it told me it was removing node as part of release-upgrade lol.

[girish]

@doodlemania2 Looks like something removed the symlink.

ln -sf /usr/local/node-16.14.2/bin/node /usr/bin/node
ln -sf /usr/local/node-16.14.2/bin/npm /usr/bin/npm

[doodlemania2]

@girish Mine shows 16.13.1 - that okay?

[girish]

@doodlemania2 yes. Maybe you are still on 7.1.x.

[doodlemania2]

@girish should i upgarde it? node is so flipping complex to upgrade

[girish]

@doodlemania2 no, it will get upgraded when you upgrade to 7.2

[doodlemania2]

@girish perfect - that fixed that! now bumping to 7.2 - thanks mate