Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-21586

Unable to start the server after the update.

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 10.2.31, 10.3.22, 10.4.12
    • 10.2.32, 10.3.23, 10.4.13
    • Server
    • None
    • CentOS 7.7 x86_64

    Description

      Hello,
      version 10.2.30 works as expected.
      But after update to 10.2.31, the can't start anymore.
      In the log files, no errors are logged.
      The only log that I can see is:

      Jan 29 07:21:53 XXX mysqld[22954]: 2020-01-29  7:21:53 140517213755584 [Note] /usr/sbin/mysqld (mysqld 10.2.31-MariaDB) starting as process 22954 ...
      		 
      Jan 29 07:21:53 XXX mysqld[22954]: 2020-01-29  7:21:53 140517213755584 [ERROR] Aborting

      The only solution was to downgrade to 10.2.30.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21600 MariaDB 10.2.31, 10.3.22, 10.4.12 as a service don't start under Windows

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          is caused by

          Task - A task that needs to be done. MDEV-11345 Compile english error messages into mysqld executable.

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            mariaTux Frank created issue -
            serg Sergei Golubchik added a comment -

            Do you have lc_messages set in your my.cnf ? Like lc_messages=de_DE, for example?

            serg Sergei Golubchik added a comment - Do you have lc_messages set in your my.cnf ? Like lc_messages=de_DE , for example?
            mariaTux Frank added a comment -

            Yes, I have found this setting in one of the config files, present under /etc/my.cnf.d/.
            Was here something changed, that will break it?
            If yes, then it will be very bad when such changes will be done in stable release stream like 10.1 or 10.2.

            mariaTux Frank added a comment - Yes, I have found this setting in one of the config files, present under /etc/my.cnf.d/. Was here something changed, that will break it? If yes, then it will be very bad when such changes will be done in stable release stream like 10.1 or 10.2.
            serg Sergei Golubchik made changes -
            Field Original Value New Value
            Fix Version/s 10.2 [ 14601 ]
            Fix Version/s 10.3 [ 22126 ]
            Fix Version/s 10.4 [ 22408 ]
            serg Sergei Golubchik made changes -
            Affects Version/s 10.4.10 [ 23907 ]
            Affects Version/s 10.3.20 [ 23909 ]
            serg Sergei Golubchik made changes -
            Assignee Vladislav Vaintroub [ wlad ]
            serg Sergei Golubchik made changes -
            Status Open [ 1 ] Confirmed [ 10101 ]
            serg Sergei Golubchik added a comment -

            This bug was introduced in MDEV-11345. Sorry for this, it'll be fixed.

            serg Sergei Golubchik added a comment - This bug was introduced in MDEV-11345 . Sorry for this, it'll be fixed.
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            Affects Version/s 10.4.12 [ 24019 ]
            Affects Version/s 10.3.22 [ 24018 ]
            Affects Version/s 10.4.10 [ 23907 ]
            Affects Version/s 10.3.20 [ 23909 ]
            serg Sergei Golubchik made changes -
            Otomatic Dominique Ottello added a comment -

            Hi,
            In the my.ini of versions 10.2.31, 10.3.22 and 10.4.12 in 32 and 64 bit, I removed the lc-messages and lc-messages-dir lines before compiling the InnoSetup installers.
            Now, there are no more problems and it works the first time after installation.
            As a result, it simplifies my task, no more need to manage the error language !
            Also think about fixing the 10.5.0 versions that have the same problem.

            Otomatic Dominique Ottello added a comment - Hi, In the my.ini of versions 10.2.31, 10.3.22 and 10.4.12 in 32 and 64 bit, I removed the lc-messages and lc-messages-dir lines before compiling the InnoSetup installers. Now, there are no more problems and it works the first time after installation. As a result, it simplifies my task, no more need to manage the error language ! Also think about fixing the 10.5.0 versions that have the same problem.
            wlad Vladislav Vaintroub made changes -
            issue.field.resolutiondate 2020-01-30 17:50:53.0 2020-01-30 17:50:53.345
            wlad Vladislav Vaintroub made changes -
            Fix Version/s 10.2.32 [ 24221 ]
            Fix Version/s 10.3.23 [ 24222 ]
            Fix Version/s 10.4.13 [ 24223 ]
            Fix Version/s 10.2 [ 14601 ]
            Fix Version/s 10.3 [ 22126 ]
            Fix Version/s 10.4 [ 22408 ]
            Resolution Fixed [ 1 ]
            Status Confirmed [ 10101 ] Closed [ 6 ]
            ralf.gebhardt Ralf Gebhardt made changes -
            ralf.gebhardt Ralf Gebhardt made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 103454 ] MariaDB v4 [ 157254 ]

            People

              wlad Vladislav Vaintroub
              mariaTux Frank
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.