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

No valid servers in cluster 'MariaDB-Monitor'

    XMLWordPrintable

Details

    • MXS-SPRINT-191

    Description

      Hi

      I'm using 2 MaxScale 22.08.3 instances in a cluster (the configuration is bellow), everything seems to be working fine, the traffic is routed properly, I could switch master/slave, GTID is the same on both DB servers.

      But the command maxctrl show maxscale on db1 shows an error in the Sync section, though checksums are the same:

      db1:

      {                                                                
          "checksum": "3ed123cc4400120c992a540745d3de675c6d4575",      
          "nodes": {                                                  
              "0cca53d01c64": "OK",                                    
              "51d4030d7309": "OK"                                    
          },                                                          
          "origin": "",                                                
          "status": "No valid servers in cluster 'MariaDB-Monitor'.",  
          "version": 1                                                
      }        
      

      db2:

      {                                                                  
          "checksum": "3ed123cc4400120c992a540745d3de675c6d4575",        
          "nodes": {                                                      
              "0cca53d01c64": "OK",                                      
              "51d4030d7309": "OK"                                        
          },                                                              
          "origin": "",                                                  
          "status": "OK",                                                
          "version": 1                                                    
      }                                                                  
      

       maxctrl list servers 

      shows that replication is ok and the DBs are ok:

      In this thread: https://groups.google.com/g/maxscale/c/ExxVP1VNMu8/m/6B6K7Z-6AAAJ?utm_medium=email&utm_source=footer
      I've been told that this may be a bug and I should report it here, so here it is

      The following configuration is used:

      # Global parameters
      [maxscale]
      # Substitute environment variables
      substitute_variables=1
      threads=1
       
      config_sync_cluster=MariaDB-Monitor
      config_sync_user=$MARIADB_MAXSCALE_USER
      config_sync_password=$MARIADB_MAXSCALE_PASSWORD
      admin_secure_gui=false
      admin_host=127.0.0.1
      max_auth_errors_until_block=0
      # Extended logging for troubleshooting. It can be activated dynamically using "maxctrl alter maxscale log_info true"
      #log_info=true
       
      # Server definitions
      [db1]
      type=server
      address=$MAXSCALE_DB1_ADDRESS
      # we use internal port of db1 server, not the exposed by docker
      port=$MAXSCALE_DB1_PORT
      protocol=MariaDBBackend
      proxy_protocol=1
      [db2]
      type=server
      address=$MAXSCALE_DB2_ADDRESS
      # we use internal port of db1 server, not the exposed by docker
      port=$MAXSCALE_DB2_PORT
      protocol=MariaDBBackend
      proxy_protocol=1
       
       
      # Monitor for the servers
      [MariaDB-Monitor]
      type=monitor
      module=mariadbmon
      servers=db1,db2
      user=$MARIADB_MAXSCALE_USER
      password=$MARIADB_MAXSCALE_PASSWORD
      monitor_interval=2s
      enforce_read_only_slaves=on
       
       
      # Service definitions
      # https://mariadb.com/kb/en/mariadb-maxscale-2208-readconnroute/
      # Readconnroute
      [Read-Conn-Service]
      type=service
      router=readconnroute
      router_options=master
      servers=db1,db2
      user=$MARIADB_MAXSCALE_USER
      password=$MARIADB_MAXSCALE_PASSWORD
      # Allow login as root
      enable_root_user=1
       
      # Listener definitions for the services
      [Read-Con-Listener]
      type=listener
      service=Read-Conn-Service
      protocol=MariaDBClient
      port=3306
      

      Attachments

        Activity

          People

            markus makela markus makela
            amid000 Dmitry
            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.