Issue Running cloudron-support --troubleshoot After Reboot

[joseph]

@roloufgoudebin looks like docker is not running systemctl start docker . And then maybe that command works after that?

[RoloufGoudebin]

Thanks! Here’s the current output of the command:

sudo cloudron-support --recreate-docker
Starting docker afresh at /var/lib/docker
Downloading addon images
/usr/bin/cloudron-support: line 742: node: command not found

[joseph]

@roloufgoudebin it seems node.js is missing. What happened to the server? Did you install any system packages?

Is /usr/local/node-20.18.0/bin/node there? If they are, run the two ln - s commands in your initial post.

[RoloufGoudebin]

ls: cannot access '/usr/local/node-20.18.0/bin/node': No such file or directory

I’ve tried both "ln" commands, but nothing works. I’m a bit desperate.

[joseph]

@RoloufGoudebin does /usr/local/ have any node versions at all?

[RoloufGoudebin]

@joseph There is version 22.20.0.
Thanks again for your help!

[joseph]

@roloufgoudebin can you try:

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

[RoloufGoudebin]

What am I supposed to do now?

sudo     ln -sf /usr/local/node-22.20.0/bin/node /usr/bin/node
ubuntu@ns3046382:/usr/local$ sudo     ln -sf /usr/local/node-22.20.0/bin/npm /usr/bin/npm
ubuntu@ns3046382:/usr/local$ sudo cloudron-support --recreate-docker
	Starting docker afresh at /var/lib/docker
	Downloading addon images
	Pulling registry.docker.com/cloudron/graphite:3.5.0@sha256:ee7c9dc49a6507cb3e3cee25495b2044908feb91dac5df87a9633dea38fdeb8a
ubuntu@ns3046382:/usr/local$ sudo cloudron-support --troubleshoot
Vendor: ASUSTeK COMPUTER INC. Product: 5001_OVH
Linux: 5.15.0-163-generic
Ubuntu: jammy 22.04
ubuntu@ns3046382:/usr/local$ 

[joseph]

@RoloufGoudebin just to take a step back. Can you give us more background as to what happened to the server? Trying to understand why node symlinks have disappeared. If you can write to me at support@cloudron.io with more details, I can take a look.

[joseph]

I investigated this on support@ . The issue was that the server had an incredibly slow disk and the iops was really bad (like 30MB/s) . The VPS provider is fixing their raid configuration .