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

Error message in case both port and socket are defined is not clear

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.2
    • Fix Version/s: 2.2.4
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-53

      Description

      When you define both socket and port for a listener you may get the following message:

      2018-02-27 13:00:00 error : Listener 'Galera-Listener', for service 'Galera-Service', already have port 7890.

      And MaxScale will shut down.

      The actual problem should be that both connection methods are defined:

      port=7890
      socket=/tmp/maxscale.sock

      The message is misleading so I'd suggest to use a more adequate one like:

      2018-02-27 13:00:00 error : Listener 'Galera-Listener', for service 'Galera-Service', Port method already defined, can't have port and socket for the same listener.

      Apparently prior to 2.2.2 this double listening method definition was not leading to a blocking error.

        Attachments

          Activity

            People

            Assignee:
            johan.wikman Johan Wikman
            Reporter:
            claudio.nanni Claudio Nanni
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.