Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Issue Running cloudron-support --troubleshoot After Reboot

Issue Running cloudron-support --troubleshoot After Reboot

Scheduled Pinned Locked Moved Unsolved Support
14 Posts 2 Posters 16 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    RoloufGoudebin
    wrote last edited by
    #5

    Here’s what the command outputs :

    Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
    
    1 Reply Last reply
    0
    • J Online
      J Online
      joseph
      Staff
      wrote last edited by
      #6

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

      1 Reply Last reply
      0
      • R Offline
        R Offline
        RoloufGoudebin
        wrote last edited by
        #7

        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
        
        
        1 Reply Last reply
        0
        • J Online
          J Online
          joseph
          Staff
          wrote last edited by
          #8

          @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.

          1 Reply Last reply
          0
          • R Offline
            R Offline
            RoloufGoudebin
            wrote last edited by
            #9
            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.

            J 1 Reply Last reply
            0
            • R 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.

              J Online
              J Online
              joseph
              Staff
              wrote last edited by
              #10

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

              1 Reply Last reply
              0
              • R Offline
                R Offline
                RoloufGoudebin
                wrote last edited by
                #11

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

                1 Reply Last reply
                0
                • J Online
                  J Online
                  joseph
                  Staff
                  wrote last edited by joseph
                  #12

                  @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
                  
                  1 Reply Last reply
                  0
                  • R Offline
                    R Offline
                    RoloufGoudebin
                    wrote last edited by
                    #13

                    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$ 
                    
                    J 1 Reply Last reply
                    0
                    • R 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$ 
                      
                      J Online
                      J Online
                      joseph
                      Staff
                      wrote last edited by
                      #14

                      @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.

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Bookmarks
                      • Search