Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3479

Disabling maxlog doesn't fully prevent it from being written to

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.9
    • Fix Version/s: 2.5.12
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-130

      Description

      When maxlog is disabled, there's always a small amount of text logged on startup. This happens because some parts of MaxScale are initialized before the variable is read from either the command line or from the configuration file.

      Here's an example of what is logged on startup when maxlog is disabled.

      MariaDB MaxScale  /home/markusjm/build-develop/log/maxscale/maxscale.log  Mon Mar 29 19:44:40 2021
      ----------------------------------------------------------------------------------------------------
      2021-03-29 19:44:40   notice : The collection of SQLite memory allocation statistics turned off.
      2021-03-29 19:44:40   notice : Threading mode of SQLite set to Multi-thread.
      2021-03-29 19:44:40   notice : Worker message queue size: 1MiB
      2021-03-29 19:44:40   notice : The logging of informational messages has been enabled.
      2021-03-29 19:44:40   notice : Using up to 4.66GiB of memory for query classifier cache
      2021-03-29 19:44:40   notice : syslog logging is enabled.
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration