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

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • 10.2.26, 10.1.41, 10.3.17, 10.4.7
    • 10.4
    • Server
    • None

    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

            People

              sanja Oleksandr Byelkin
              hholzgra Hartmut Holzgraefe
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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