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. MySQL Not starting after update

MySQL Not starting after update

Scheduled Pinned Locked Moved Solved Support
8 Posts 3 Posters 852 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.
    • A Offline
      A Offline
      AniTexs
      wrote on last edited by
      #1

      MySQL service is just saying

      2022-12-08T13:37:54.000Z Waiting for MySQL to come up
      

      How can I help it?
      Tried rebooting the server, no help there sadly.

      1 Reply Last reply
      0
      • A Offline
        A Offline
        AniTexs
        wrote on last edited by
        #2

        I get this error in the BOX Logs

        Dec 08 14:35:08 box:cloudron Startup task at index 2 failed: Network error waiting for mysql: connect ECONNREFUSED 172.18.0.3:3000 BoxError: Network error waiting for mysql: connect ECONNREFUSED 172.18.0.3:3000
        at /home/yellowtent/box/src/services.js:588:33
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (node:internal/process/task_queues:96:5)
        at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20)
        at async waitForContainer (/home/yellowtent/box/src/services.js:583:5)
        at async startMysql (/home/yellowtent/box/src/services.js:1150:9)
        at async Object.startServices (/home/yellowtent/box/src/services.js:806:9)
        at async Object.start (/home/yellowtent/box/src/platform.js:67:13)
        at async onActivated (/home/yellowtent/box/src/cloudron.js:79:5)
        at async Array.<anonymous> (/home/yellowtent/box/src/cloudron.js:130:9)
        
        A 1 Reply Last reply
        0
        • A Offline
          A Offline
          AniTexs
          wrote on last edited by
          #3

          Tried updating server using apt update & apt upgrade
          This is what apt list --upgradables returned

          apt-utils/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8]
          apt/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8]
          base-files/focal-updates 11ubuntu5.6 amd64 [upgradable from: 11ubuntu5.5]
          distro-info-data/focal-updates,focal-updates 0.43ubuntu1.11 all [upgradable from: 0.43ubuntu1.10]
          keyutils/focal-updates 1.6-6ubuntu1.1 amd64 [upgradable from: 1.6-6ubuntu1]
          language-pack-en-base/focal-updates,focal-updates 1:20.04+20220818 all [upgradable from: 1:20.04+20220211]
          language-pack-en/focal-updates,focal-updates 1:20.04+20220818 all [upgradable from: 1:20.04+20220211]
          language-pack-gnome-en-base/focal-updates,focal-updates 1:20.04+20220818 all [upgradable from: 1:20.04+20220211]
          language-pack-gnome-en/focal-updates,focal-updates 1:20.04+20220818 all [upgradable from: 1:20.04+20220211]
          libapt-pkg6.0/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8]
          libasn1-8-heimdal/focal-updates,focal-security 7.7.0+dfsg-1ubuntu1.2 amd64 [upgradable from: 7.7.0+dfsg-1ubuntu1.1]
          libgssapi3-heimdal/focal-updates,focal-security 7.7.0+dfsg-1ubuntu1.2 amd64 [upgradable from: 7.7.0+dfsg-1ubuntu1.1]
          libhcrypto4-heimdal/focal-updates,focal-security 7.7.0+dfsg-1ubuntu1.2 amd64 [upgradable from: 7.7.0+dfsg-1ubuntu1.1]
          libheimbase1-heimdal/focal-updates,focal-security 7.7.0+dfsg-1ubuntu1.2 amd64 [upgradable from: 7.7.0+dfsg-1ubuntu1.1]
          libheimntlm0-heimdal/focal-updates,focal-security 7.7.0+dfsg-1ubuntu1.2 amd64 [upgradable from: 7.7.0+dfsg-1ubuntu1.1]
          libhx509-5-heimdal/focal-updates,focal-security 7.7.0+dfsg-1ubuntu1.2 amd64 [upgradable from: 7.7.0+dfsg-1ubuntu1.1]
          libkeyutils1/focal-updates 1.6-6ubuntu1.1 amd64 [upgradable from: 1.6-6ubuntu1]
          libkrb5-26-heimdal/focal-updates,focal-security 7.7.0+dfsg-1ubuntu1.2 amd64 [upgradable from: 7.7.0+dfsg-1ubuntu1.1]
          libmysqlclient21/focal-updates 8.0.31-0ubuntu0.20.04.2 amd64 [upgradable from: 8.0.31-0ubuntu0.20.04.1]
          libnetplan0/focal-updates 0.104-0ubuntu2~20.04.2 amd64 [upgradable from: 0.104-0ubuntu2~20.04.1]
          libnotify4/focal-updates 0.7.9-1ubuntu3.20.04.2 amd64 [upgradable from: 0.7.9-1ubuntu2]
          libroken18-heimdal/focal-updates,focal-security 7.7.0+dfsg-1ubuntu1.2 amd64 [upgradable from: 7.7.0+dfsg-1ubuntu1.1]
          libsnmp-base/focal-updates,focal-updates 5.8+dfsg-2ubuntu2.5 all [upgradable from: 5.8+dfsg-2ubuntu2.4]
          libsnmp35/focal-updates 5.8+dfsg-2ubuntu2.5 amd64 [upgradable from: 5.8+dfsg-2ubuntu2.4]
          libudev1/focal-updates 245.4-4ubuntu3.19 amd64 [upgradable from: 245.4-4ubuntu3.17]
          libwind0-heimdal/focal-updates,focal-security 7.7.0+dfsg-1ubuntu1.2 amd64 [upgradable from: 7.7.0+dfsg-1ubuntu1.1]
          linux-firmware/focal-updates,focal-updates 1.187.35 all [upgradable from: 1.187.31]
          mysql-client-8.0/focal-updates 8.0.31-0ubuntu0.20.04.2 amd64 [upgradable from: 8.0.31-0ubuntu0.20.04.1]
          mysql-client-core-8.0/focal-updates 8.0.31-0ubuntu0.20.04.2 amd64 [upgradable from: 8.0.31-0ubuntu0.20.04.1]
          mysql-server-8.0/focal-updates 8.0.31-0ubuntu0.20.04.2 amd64 [upgradable from: 8.0.31-0ubuntu0.20.04.1]
          mysql-server-core-8.0/focal-updates 8.0.31-0ubuntu0.20.04.2 amd64 [upgradable from: 8.0.31-0ubuntu0.20.04.1]
          netplan.io/focal-updates 0.104-0ubuntu2~20.04.2 amd64 [upgradable from: 0.104-0ubuntu2~20.04.1]
          python-apt-common/focal-updates,focal-updates 2.0.0ubuntu0.20.04.8 all [upgradable from: 2.0.0ubuntu0.20.04.7]
          python3-apt/focal-updates 2.0.0ubuntu0.20.04.8 amd64 [upgradable from: 2.0.0ubuntu0.20.04.7]
          python3-distupgrade/focal-updates,focal-updates 1:20.04.39 all [upgradable from: 1:20.04.38]
          ubuntu-advantage-tools/focal-updates 27.12~20.04.1 amd64 [upgradable from: 27.8~20.04.1]
          ubuntu-release-upgrader-core/focal-updates,focal-updates 1:20.04.39 all [upgradable from: 1:20.04.38]
          udev/focal-updates 245.4-4ubuntu3.19 amd64 [upgradable from: 245.4-4ubuntu3.17]
          unattended-upgrades/focal-updates,focal-updates 2.3ubuntu0.3 all [upgradable from: 2.3ubuntu0.1]
          
          1 Reply Last reply
          0
          • A AniTexs

            I get this error in the BOX Logs

            Dec 08 14:35:08 box:cloudron Startup task at index 2 failed: Network error waiting for mysql: connect ECONNREFUSED 172.18.0.3:3000 BoxError: Network error waiting for mysql: connect ECONNREFUSED 172.18.0.3:3000
            at /home/yellowtent/box/src/services.js:588:33
            at runMicrotasks (<anonymous>)
            at processTicksAndRejections (node:internal/process/task_queues:96:5)
            at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20)
            at async waitForContainer (/home/yellowtent/box/src/services.js:583:5)
            at async startMysql (/home/yellowtent/box/src/services.js:1150:9)
            at async Object.startServices (/home/yellowtent/box/src/services.js:806:9)
            at async Object.start (/home/yellowtent/box/src/platform.js:67:13)
            at async onActivated (/home/yellowtent/box/src/cloudron.js:79:5)
            at async Array.<anonymous> (/home/yellowtent/box/src/cloudron.js:130:9)
            
            A Offline
            A Offline
            AniTexs
            wrote on last edited by
            #4

            @AniTexs said in MySQL Not starting after update:

            I get this error in the BOX Logs

            Dec 08 14:35:08 box:cloudron Startup task at index 2 failed: Network error waiting for mysql: connect ECONNREFUSED 172.18.0.3:3000 BoxError: Network error waiting for mysql: connect ECONNREFUSED 172.18.0.3:3000
            at /home/yellowtent/box/src/services.js:588:33
            at runMicrotasks (<anonymous>)
            at processTicksAndRejections (node:internal/process/task_queues:96:5)
            at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20)
            at async waitForContainer (/home/yellowtent/box/src/services.js:583:5)
            at async startMysql (/home/yellowtent/box/src/services.js:1150:9)
            at async Object.startServices (/home/yellowtent/box/src/services.js:806:9)
            at async Object.start (/home/yellowtent/box/src/platform.js:67:13)
            at async onActivated (/home/yellowtent/box/src/cloudron.js:79:5)
            at async Array.<anonymous> (/home/yellowtent/box/src/cloudron.js:130:9)
            

            Still the same issue as this....

            1 Reply Last reply
            0
            • nebulonN Away
              nebulonN Away
              nebulon
              Staff
              wrote on last edited by
              #5

              Generally one should not run apt manually. Cloudron will automatically apply security updates. Updating or installing packages manually may break the instance.

              In your case however the mysql in question anyways runs within its own container, so it is decoupled from the host system.

              Can you run /home/yellowtent/box/setup/start.sh as root on the system and see if this fixes things up?

              A 1 Reply Last reply
              0
              • nebulonN nebulon marked this topic as a question on
              • nebulonN nebulon

                Generally one should not run apt manually. Cloudron will automatically apply security updates. Updating or installing packages manually may break the instance.

                In your case however the mysql in question anyways runs within its own container, so it is decoupled from the host system.

                Can you run /home/yellowtent/box/setup/start.sh as root on the system and see if this fixes things up?

                A Offline
                A Offline
                AniTexs
                wrote on last edited by
                #6

                @nebulon Sadly not..
                Heres the output of the script.

                root@vmi260777:~# /home/yellowtent/box/setup/start.sh
                2022-12-08T14:46:10 ==> start: Cloudron Start
                media:x:500:
                2022-12-08T14:46:10 ==> 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-12-08T14:46:11 ==> start: Ensuring directories
                2022-12-08T14:46:11 ==> start: Configuring journald
                2022-12-08T14:46:11 ==> start: Setting up unbound
                2022-12-08T14:46:11 ==> 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-12-08T14:46:15 ==> start: Configuring sudoers
                2022-12-08T14:46:15 ==> start: Configuring collectd
                2022-12-08T14:46:15 ==> start: Configuring sysctl
                2022-12-08T14:46:15 ==> start: Configuring logrotate
                2022-12-08T14:46:15 ==> start: Adding motd message for admins
                2022-12-08T14:46:15 ==> start: Configuring nginx
                2022-12-08T14:46:16 ==> 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-12-08T14:46:16 ==> start: Migrating data
                Ignoring invalid configuration option passed to Connection: driver. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
                [INFO] No migrations to run
                [INFO] Done
                2022-12-08T14:46:16 ==> start: Changing ownership
                2022-12-08T14:46:16 ==> start: Starting Cloudron
                2022-12-08T14:46:18 ==> start: Almost done
                
                girishG 1 Reply Last reply
                0
                • A AniTexs

                  @nebulon Sadly not..
                  Heres the output of the script.

                  root@vmi260777:~# /home/yellowtent/box/setup/start.sh
                  2022-12-08T14:46:10 ==> start: Cloudron Start
                  media:x:500:
                  2022-12-08T14:46:10 ==> 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-12-08T14:46:11 ==> start: Ensuring directories
                  2022-12-08T14:46:11 ==> start: Configuring journald
                  2022-12-08T14:46:11 ==> start: Setting up unbound
                  2022-12-08T14:46:11 ==> 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-12-08T14:46:15 ==> start: Configuring sudoers
                  2022-12-08T14:46:15 ==> start: Configuring collectd
                  2022-12-08T14:46:15 ==> start: Configuring sysctl
                  2022-12-08T14:46:15 ==> start: Configuring logrotate
                  2022-12-08T14:46:15 ==> start: Adding motd message for admins
                  2022-12-08T14:46:15 ==> start: Configuring nginx
                  2022-12-08T14:46:16 ==> 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-12-08T14:46:16 ==> start: Migrating data
                  Ignoring invalid configuration option passed to Connection: driver. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection
                  [INFO] No migrations to run
                  [INFO] Done
                  2022-12-08T14:46:16 ==> start: Changing ownership
                  2022-12-08T14:46:16 ==> start: Starting Cloudron
                  2022-12-08T14:46:18 ==> start: Almost done
                  
                  girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #7

                  @AniTexs Looks like this is the mysql addon/service that is not starting ? Please try this https://docs.cloudron.io/troubleshooting/#mysql-addon

                  A 1 Reply Last reply
                  0
                  • girishG girish

                    @AniTexs Looks like this is the mysql addon/service that is not starting ? Please try this https://docs.cloudron.io/troubleshooting/#mysql-addon

                    A Offline
                    A Offline
                    AniTexs
                    wrote on last edited by
                    #8

                    @girish I restored from a backup to get it working..

                    1 Reply Last reply
                    0
                    • nebulonN nebulon 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