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

MaxScale fails to start and doesn't log any useful message when there are spurious characters in the config file

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.4.3
    • 2.0.0
    • Core
    • None
    • 2016-10

    Description

      In maxscale.cnf, if I add anywhere:

      ....
      any_string_without_equal_sign
      ....

      MaxScale refuses to start but in the error log there is no evidence of misconfiguration:

      May 10 18:38:10 dhcppc6 maxscale[2187]: Finished MaxScale log flusher.
      May 10 18:38:11 dhcppc6 maxscale[2187]: MaxScale received signal SIGTERM. Exiting.
      May 10 18:38:11 dhcppc6 maxscale[2187]: MaxScale is shutting down.
      May 10 18:38:11 dhcppc6 maxscale[2187]: MaxScale shutdown completed.

      I think MaxScale should point out at the misconfiguration.

      While if you add an option like:

      ....
      blah=123
      ....

      It starts but doesn't complain at all.

      Attachments

        Activity

          People

            markus makela markus makela
            claudio.nanni Claudio Nanni
            Votes:
            0 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.