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

Maxadmin shows wrong monitor status

    XMLWordPrintable

    Details

    • Sprint:
      MXS-SPRINT-86

      Description

      After MaxScale upgrade 2.2.20 -> 2.3.5 Maxadmin and JSON started to show wrong MariaDB-Monitor status (Stopped instead of Running). Maxctrl do not affected with this bug:

      root@ims# maxctrl list monitors
      ┌─────────────────┬─────────┬────────────┐
      │ Monitor         │ State   │ Servers    │
      ├─────────────────┼─────────┼────────────┤
      │ MariaDB-Monitor │ Running │ ims1, ims2 │
      └─────────────────┴─────────┴────────────┘
      root@ims# maxadmin list monitors                    
      ---------------------+--------------------
      Monitor              | Status
      ---------------------+--------------------
      MariaDB-Monitor      | Stopped
      ---------------------+--------------------
      root@ims# maxadmin shutdown monitor MariaDB-Monitor
      root@ims# maxctrl list monitors                    
      ┌─────────────────┬─────────┬────────────┐
      │ Monitor         │ State   │ Servers    │
      ├─────────────────┼─────────┼────────────┤
      │ MariaDB-Monitor │ Stopped │ ims1, ims2 │
      └─────────────────┴─────────┴────────────┘
      root@ims# maxadmin list monitors                   
      ---------------------+---------------------
      Monitor              | Status
      ---------------------+---------------------
      MariaDB-Monitor      | Stopped
      ---------------------+---------------------
      root@ims# maxadmin restart monitor MariaDB-Monitor 
      root@ims# maxctrl list monitors                   
      ┌─────────────────┬─────────┬────────────┐
      │ Monitor         │ State   │ Servers    │
      ├─────────────────┼─────────┼────────────┤
      │ MariaDB-Monitor │ Running │ ims1, ims2 │
      └─────────────────┴─────────┴────────────┘
      root@ims# maxadmin list monitors                  
      ---------------------+--------------------
      Monitor              | Status
      ---------------------+--------------------
      MariaDB-Monitor      | Stopped
      ---------------------+--------------------
       
      root@ims# maxadmin show monitor MariaDB-Monitor
      Monitor:                0x561abe342bc0
      Name:                   MariaDB-Monitor
      State:                  Running
      Times monitored:        3070
      Sampling interval:      2000 milliseconds
      Connect Timeout:        3 seconds
      Read Timeout:           1 seconds
      Write Timeout:          2 seconds
      Connect attempts:       1 
      Monitored servers:      [ims1]:3306, [ims2]:3306
      Automatic failover:     Disabled
      Failcount:              5
      Failover timeout:       90
      Switchover timeout:     90
      Automatic rejoin:       Disabled
      Enforce read-only:      Disabled
      Detect stale master:    Enabled
       
      Server information:
      -------------------
      

      Config:

      [MariaDB-Monitor]
      type=monitor
      module=mariadbmon
      servers=ims1,ims2
      user=******
      password=*******
      monitor_interval=2000
      

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            artlov Arthur Kono
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: