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

Print the real version in the error log

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.2(EOL)
    • 10.2.2
    • OTHER
    • None
    • 10.2.0-6, 10.2.0-7, 10.2.2-2

    Description

      It's related to MDEV-7780 where @@version has become writable.

      I don't know if it's technically possible, but if it is, it would be extremely useful to additionally print the real version (one returned by mysqld --version without an argument) in the error log upon startup and, better still, also upon a crash. We are going to have major problem with users setting this variable, because they will set it in the config file, will never update it in a timely manner (naturally, because they can get upgrades automatically), and we won't know which real version they report their problem against, finding it out will require additional negotiations and won't always be successful.

      Attachments

        Issue Links

          causes

          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
          relates to

          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-6873 On startup please make MariaDB report it's version number

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

          Task - A task that needs to be done. MDEV-7780 Support for faking server version

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

          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-20287 Have the server process print a "starting mysql" message before first actual log message

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

          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

          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

          Activity

            Ascending order - Click to sort in descending order
            svoj Sergey Vojtovich added a comment -

            We should also fix the problem mentioned in the following commit by using real version:
            https://github.com/MariaDB/server/commit/70a4856df8c2af14e2d0a32b8d49bbd2bd2fc464

            svoj Sergey Vojtovich added a comment - We should also fix the problem mentioned in the following commit by using real version: https://github.com/MariaDB/server/commit/70a4856df8c2af14e2d0a32b8d49bbd2bd2fc464
            svoj Sergey Vojtovich added a comment -

            serg, please review fix for this bug.

            svoj Sergey Vojtovich added a comment - serg , please review fix for this bug.
            svoj Sergey Vojtovich added a comment -

            serg, this task was supposed to be in this current sprint. Not sure why it wasn't added.

            svoj Sergey Vojtovich added a comment - serg , this task was supposed to be in this current sprint. Not sure why it wasn't added.

            People

              svoj Sergey Vojtovich
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.