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. After update to 7.3.2, mySQL does not come up

After update to 7.3.2, mySQL does not come up

Scheduled Pinned Locked Moved Solved Support
mysqladdons
6 Posts 3 Posters 1.6k 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.
  • necrevistonnezrN Offline
    necrevistonnezrN Offline
    necrevistonnezr
    wrote on last edited by girish
    #1

    After the update to 7.3.2, mySQL does not come up

    MySQL on the host runs fine.

    MySQL (addon) displays the following error:

    2022-10-17T15:47:50.522815Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
    2022-10-17T15:47:50.522854Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30-0ubuntu0.20.04.2) starting as process 11
    2022-10-17T15:47:50.545100Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
    2022-10-17T15:47:50.846784Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with MySQL 8.0.28, and it appears logically non empty. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html
    2022-10-17T15:47:50.846868Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
    2022-10-17T15:47:51.175047Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
    2022-10-17T15:47:51.175383Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
    2022-10-17T15:47:51.175427Z 0 [ERROR] [MY-010119] [Server] Aborting
    2022-10-17T15:47:51.176673Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.30-0ubuntu0.20.04.2)  (Ubuntu).
    

    What to do?

    robiR 1 Reply Last reply
    0
    • necrevistonnezrN necrevistonnezr

      After the update to 7.3.2, mySQL does not come up

      MySQL on the host runs fine.

      MySQL (addon) displays the following error:

      2022-10-17T15:47:50.522815Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
      2022-10-17T15:47:50.522854Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30-0ubuntu0.20.04.2) starting as process 11
      2022-10-17T15:47:50.545100Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
      2022-10-17T15:47:50.846784Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with MySQL 8.0.28, and it appears logically non empty. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html
      2022-10-17T15:47:50.846868Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
      2022-10-17T15:47:51.175047Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
      2022-10-17T15:47:51.175383Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
      2022-10-17T15:47:51.175427Z 0 [ERROR] [MY-010119] [Server] Aborting
      2022-10-17T15:47:51.176673Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.30-0ubuntu0.20.04.2)  (Ubuntu).
      

      What to do?

      robiR Offline
      robiR Offline
      robi
      wrote on last edited by
      #2

      @necrevistonnezr See the bottom of https://dev.mysql.com/doc/refman/8.0/en/upgrade-troubleshooting.html

      Conscious tech

      necrevistonnezrN 1 Reply Last reply
      1
      • robiR robi

        @necrevistonnezr See the bottom of https://dev.mysql.com/doc/refman/8.0/en/upgrade-troubleshooting.html

        necrevistonnezrN Offline
        necrevistonnezrN Offline
        necrevistonnezr
        wrote on last edited by
        #3

        @robi thanks, I followed the instructions at https://docs.cloudron.io/troubleshooting/#mysql-addon and it worked…

        robiR 1 Reply Last reply
        0
        • necrevistonnezrN necrevistonnezr marked this topic as a question on
        • necrevistonnezrN necrevistonnezr has marked this topic as solved on
        • necrevistonnezrN necrevistonnezr

          @robi thanks, I followed the instructions at https://docs.cloudron.io/troubleshooting/#mysql-addon and it worked…

          robiR Offline
          robiR Offline
          robi
          wrote on last edited by
          #4

          @necrevistonnezr cool, so a clean shutdown and start resolved it?

          Conscious tech

          necrevistonnezrN 1 Reply Last reply
          0
          • robiR robi

            @necrevistonnezr cool, so a clean shutdown and start resolved it?

            necrevistonnezrN Offline
            necrevistonnezrN Offline
            necrevistonnezr
            wrote on last edited by necrevistonnezr
            #5

            @robi No, I was referring to stopping mysql, moving the folder, restarting mysql and then restoring app backups...

            In case of disk corruption errors, it's best to just start afresh if you have uptodate backups.

            docker stop mysql
            mv /home/yellowtent/platformdata/mysql /home/yellowtent/platformdata/mysql-copy
            mkdir /home/yellowtent/platformdata/mysql
            docker restart mysql
            

            Then, just restore the apps one by one from the latest backup.

            @girish You might want to check if

             innodb_fast_shutdown=2
            

            is a good setting (see https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html)

            girishG 1 Reply Last reply
            1
            • necrevistonnezrN necrevistonnezr

              @robi No, I was referring to stopping mysql, moving the folder, restarting mysql and then restoring app backups...

              In case of disk corruption errors, it's best to just start afresh if you have uptodate backups.

              docker stop mysql
              mv /home/yellowtent/platformdata/mysql /home/yellowtent/platformdata/mysql-copy
              mkdir /home/yellowtent/platformdata/mysql
              docker restart mysql
              

              Then, just restore the apps one by one from the latest backup.

              @girish You might want to check if

               innodb_fast_shutdown=2
              

              is a good setting (see https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html)

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

              @necrevistonnezr I wasn't aware of the setting, good to know.

              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