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. Cloudron on 18.04.5 - GLIBC_2.28 not found (required by node)

Cloudron on 18.04.5 - GLIBC_2.28 not found (required by node)

Scheduled Pinned Locked Moved Solved Support
nodeupgrade
12 Posts 5 Posters 10.4k Views 5 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.
  • BrutalBirdieB BrutalBirdie
    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.

    BrutalBirdieB Offline
    BrutalBirdieB Offline
    BrutalBirdie
    Partner
    wrote on last edited by BrutalBirdie
    #2

    Looks like Ubuntu 18.04.05 is the issue.
    Attempting upgrade to 20.04 to fix the Issue.

    Like my work? Consider donating a drink. Cheers!

    BrutalBirdieB 1 Reply Last reply
    0
    • BrutalBirdieB BrutalBirdie

      Looks like Ubuntu 18.04.05 is the issue.
      Attempting upgrade to 20.04 to fix the Issue.

      BrutalBirdieB Offline
      BrutalBirdieB Offline
      BrutalBirdie
      Partner
      wrote on last edited by
      #3

      Upgrade to Ubuntu 20.04 solved the Issue.

      Like my work? Consider donating a drink. Cheers!

      1 Reply Last reply
      0
      • BrutalBirdieB BrutalBirdie marked this topic as a question on
      • BrutalBirdieB BrutalBirdie has marked this topic as solved on
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #4

        Yes this is the reason why we stopped supporting Ubuntu 18 😕

        See also https://forum.cloudron.io/post/68921

        BrutalBirdieB 1 Reply Last reply
        2
        • nebulonN nebulon

          Yes this is the reason why we stopped supporting Ubuntu 18 😕

          See also https://forum.cloudron.io/post/68921

          BrutalBirdieB Offline
          BrutalBirdieB Offline
          BrutalBirdie
          Partner
          wrote on last edited by
          #5

          @nebulon happend on a server with Cloudron version v7.4.2 tho 🤔

          Like my work? Consider donating a drink. Cheers!

          1 Reply Last reply
          0
          • girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #6

            Can you check node --version ? I think this is supposed to happen only with node 18 (which is in Cloudron 7.5.0)

            1 Reply Last reply
            0
            • C Offline
              C Offline
              Cetheus
              wrote on last edited by
              #7

              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.

              1 Reply Last reply
              1
              • girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #8

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

                1 Reply Last reply
                1
                • RazielKanosR Offline
                  RazielKanosR Offline
                  RazielKanos
                  wrote on last edited by
                  #9

                  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!

                  C 1 Reply Last reply
                  2
                  • RazielKanosR RazielKanos

                    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!

                    C Offline
                    C Offline
                    Cetheus
                    wrote on last edited by
                    #10

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

                    1 Reply Last reply
                    1
                    • C Offline
                      C Offline
                      Cetheus
                      wrote on last edited by
                      #11

                      Thanks for all your help.
                      The Server is up and running again 🙂

                      1 Reply Last reply
                      1
                      • nebulonN Offline
                        nebulonN Offline
                        nebulon
                        Staff
                        wrote on last edited by
                        #12

                        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.

                        1 Reply Last reply
                        2
                        • girishG girish referenced this topic on
                        • girishG girish referenced this topic 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