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
  • 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. Trouble upgrading from Ubuntu 18.04 to 20.04

Trouble upgrading from Ubuntu 18.04 to 20.04

Scheduled Pinned Locked Moved Solved Support
ubuntuupgrade
8 Posts 2 Posters 1.2k Views 3 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.
    • doodlemania2D Offline
      doodlemania2D Offline
      doodlemania2
      App Dev
      wrote on last edited by girish
      #1

      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?

      doodlemania2D 1 Reply Last reply
      0
      • doodlemania2D 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
        media❌500:
        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.

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #3

        @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
        
        doodlemania2D 1 Reply Last reply
        0
        • doodlemania2D 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?

          doodlemania2D Offline
          doodlemania2D Offline
          doodlemania2
          App Dev
          wrote on last edited by
          #2

          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
          media❌500:
          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.

          girishG 1 Reply Last reply
          0
          • doodlemania2D 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
            media❌500:
            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.

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #3

            @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
            
            doodlemania2D 1 Reply Last reply
            0
            • girishG 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
              
              doodlemania2D Offline
              doodlemania2D Offline
              doodlemania2
              App Dev
              wrote on last edited by
              #4

              @girish Mine shows 16.13.1 - that okay?

              girishG 1 Reply Last reply
              0
              • doodlemania2D doodlemania2

                @girish Mine shows 16.13.1 - that okay?

                girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #5

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

                doodlemania2D 1 Reply Last reply
                0
                • girishG girish

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

                  doodlemania2D Offline
                  doodlemania2D Offline
                  doodlemania2
                  App Dev
                  wrote on last edited by
                  #6

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

                  girishG 1 Reply Last reply
                  0
                  • doodlemania2D doodlemania2

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

                    girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by
                    #7

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

                    doodlemania2D 1 Reply Last reply
                    0
                    • girishG girish

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

                      doodlemania2D Offline
                      doodlemania2D Offline
                      doodlemania2
                      App Dev
                      wrote on last edited by
                      #8

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

                      1 Reply Last reply
                      0
                      • girishG girish marked this topic as a question on
                      • girishG girish has marked this topic as solved on
                      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