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

Syslog output is not filtered according to current log configuration

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.10
    • Fix Version/s: 2.5.11
    • Component/s: Core
    • Labels:
      None

      Description

      Syslog messages are not filtered according to the current log configuration. As a result, all messages are logged into syslog which results in poor performance. To prevent this from happening, add syslog=false to the configuration

      This happened because of a bug where session_trace was always enabled and the code that checked whether a message should be logged always thought the message should be processed.

        Attachments

          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