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

Some configuration cause no errors to be logged

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 22.08.4, 23.02.1
    • 22.08.5, 23.02.2
    • Core
    • None

    Description

      Starting with 22.08, MaxScale will validate most of the configuration very early in the startup process. This means that duplicate sections and duplicate parameter values are detected much earlier. For these types of errors, no log messages are written into the MaxScale log. This causes configuration problems like this to be very hard to detect as repeated restarts of MaxScale do not appear to leave a trace in the systemd journal.

      The reason for the missing journal messages might be a separate bug but the fact that no log messages are written makes it a more severe one. Older versions of MaxScale logged errors in the log whenever a problem like this was found. However, they also exhibited much stranger behavior where duplicate values were concatenated to form invalid values.

      Attachments

        Activity

          People

            markus makela markus makela
            markus makela markus makela
            Votes:
            1 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.