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

/maxscale/logs/data endpoint doesn't filter syslog contents correctly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.4.2, 22.08.1
    • Fix Version/s: 6.4.4, 22.08.2
    • Component/s: REST-API
    • Labels:
      None

      Description

      The contents of the log are not filtered correctly and the response payload may contain either messages from older MaxScale versions with a different log message structure or from the audit daemon if MaxScale has crashed or hits a debug assertion.

      Currently the matching is done by filtering with _COMM=maxscale but this will also include any auditing messages logged for the MaxScale process. The correct thing would be to also filter on the SYSLOG_IDENTIFIER field to make sure only matching messages are logged. Matching both _COMM and SYSLOG_IDENTIGIER avoids the problem where something other than MaxScale is using the maxscale syslog identifier.

        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

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