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

Servers appearing as Stale out of list servers for a fresh setup

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 2.2.1
    • Component/s: Core
    • Labels:
      None
    • Environment:
      CentOS 7.2

      Description

      Folks,

      I raised a new environment with pretty basic configs, comprising of one master and one slave, and a dedicated VM for Maxscale. With dyamic commands I created the monitor, listener and created and added the servers. As it's mandatory for 2.2, I started Maxscale with --user=root.

      What I think is strange about this setup is that the servers out of list servers have the Stale status all the time, no matter what I do, it's there:

      [root@maxscale maxscale.cnf.d]# maxadmin list servers
      Servers.
      -------------------+-----------------+-------+-------------+--------------------
      Server             | Address         | Port  | Connections | Status
      -------------------+-----------------+-------+-------------+--------------------
      prod_mariadb01     | 192.168.50.11   |  3306 |           0 | Master, Stale Status, Running
      prod_mariadb02     | 192.168.50.12   |  3306 |           0 | Slave, Stale Status, Running
      -------------------+-----------------+-------+-------------+--------------------
      

      Is it this way? Thanks!

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            wagnerbianchi Wagner Bianchi (Inactive)
            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.