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

MaxScale unconditionally loads global options from /etc/maxscale.cnf.d/maxscale.cnf

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.16
    • Fix Version/s: 2.4.19, 2.5.17
    • Component/s: Core
    • Labels:
      None

      Description

      If the file /etc/maxscale.cnf.d/maxscale.cnf exists and it contains a [maxscale] section, the file is loaded as if it were a persisted file when it isn't. If the file contains no errors, it is successfully loaded after which the normal file processing proceeds to detect a duplicate section which then causes a misleading error message to be logged. The correct thing to do would be to only use the global config handler for persisted files called maxscale.cnf and only run the global config handler for them, not both.

        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.