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

Have the server process print a "starting mysql" message before first actual log message

Details

    Description

      Right now server log output just starts with whatever log message comes out first.

      Depending on configuration typically the first startup message you'll see will be

      [Note] InnoDB: Using Linux native AIO

      But that's nothing you can rely on.

      Especially in cases where mysqld was killed hard (kill -9, OOM kill, machine failure), there's no clear "old instance messages end here, new instance log starts" distinction that can easily be searched for.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-6873 On startup please make MariaDB report it's version number

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-9593 Print the real version in the error log

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-10967 Print the real version in the error log #2

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-17093 Print version_source_revision in the error log upon server startup

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21046 Print server version to error log instead of stderr during startup process

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-21711 Log: "Server Version xx.xx.xx starting" as very first thing when an instance is starting

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-10648 mysqld --log-error prints on stdout at start

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Confirmed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20344 startup messages belong in stderr/error-log not stdout

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            hholzgra Hartmut Holzgraefe added a comment -

            Would also be nice to have the version number in the very first and very last message, to make it more easy to spot where a version change happened in a larger error log ...

            hholzgra Hartmut Holzgraefe added a comment - Would also be nice to have the version number in the very first and very last message, to make it more easy to spot where a version change happened in a larger error log ...
            GeoffMontee Geoff Montee (Inactive) added a comment -

            MDEV-21046 is related to this as well.

            GeoffMontee Geoff Montee (Inactive) added a comment - MDEV-21046 is related to this as well.
            danblack Daniel Black added a comment -

            Corrected in https://github.com/MariaDB/server/pull/1979

            danblack Daniel Black added a comment - Corrected in https://github.com/MariaDB/server/pull/1979
            hholzgra Hartmut Holzgraefe added a comment -

            Actually fixed since 10.3.38, 10.4.28, 10.5.19, 10.6.12 AFAICT

            hholzgra Hartmut Holzgraefe added a comment - Actually fixed since 10.3.38, 10.4.28, 10.5.19, 10.6.12 AFAICT

            People

              sanja Oleksandr Byelkin
              hholzgra Hartmut Holzgraefe
              Votes:
              2 Vote for this issue
              Watchers:
              6 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.