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

Server fails to start with mysqld_multi with mysqld_safe options

Details

    Description

      If you try to start 10.3.20 using mysqld_multi, and if the [mysqld_safe] option group in the config file contains options that are not supported by mysqld, then it will fail to start. For example, let's say that you provide the --numa_interleave option:

      [mysqld_safe]
      numa_interleave
      

      Then you would see the following error message:

      [ERROR] /usr/local/mysql/bin/mysqld: unknown option '--numa_interleave'
      

      After removing the options that mysqld doesn't support from the config file, it will start normally.

      Attachments

        Issue Links

          Activity

            ok to push after you have checked buildbot results.

            jplindst Jan Lindström (Inactive) added a comment - ok to push after you have checked buildbot results.
            sysprg Julius Goryavsky added a comment - Fixed, https://github.com/MariaDB/server/commit/5796021174fd7096267003b999e02d6cf98f555b

            Fix does not work. Please test fix locally first using provided steps.

            jplindst Jan Lindström (Inactive) added a comment - Fix does not work. Please test fix locally first using provided steps.

            ok to push.

            jplindst Jan Lindström (Inactive) added a comment - ok to push.
            sysprg Julius Goryavsky added a comment - Fixed, https://github.com/MariaDB/server/commit/bf303e824cec48e10eba18c5dab86a8cdd1af850

            People

              sysprg Julius Goryavsky
              kjoiner Kyle Joiner (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              7 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.