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

keine Verbindung zum Server / no connection to server

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not a Bug
    • Affects Version/s: 2.5.13
    • Fix Version/s: N/A
    • Component/s: N/A
    • Labels:
      None
    • Environment:
      SLES 15

      Description

      Nach Upgrade von Maxscale 2.4 auf 2.5 erkennt maxscale den Datenbankserver nicht mehr. Daraufhin haben wir die Konfiguration reduziert bis auf:

      ## Definition of the servers
      [maxscale]
      threads=auto
      log_info=true
       
      [zd-dbsrv-1]
      type=server
      address=134.100.***.***
      port=3306
       
      [Standard]
      type=service
      router=readconnroute
      servers=zd-dbsrv-1
      user=maxscale
      password=******
      enable_root_user=0
       
      [Standard-Listener]
      type=listener
      service=Standard
      protocol=mariadbclient
      port=3306
      address=0.0.0.0
      

      maxctrl sagt: Server Down
      Log-Datei:

      MariaDB MaxScale  /var/log/maxscale/maxscale.log  Wed Jul 14 14:57:12 2021
      ----------------------------------------------------------------------------
      2021-07-14 14:57:12   notice : The systemd watchdog is Enabled. Internal timeout = 30s
      2021-07-14 14:57:12   notice : Worker message queue size: 1MiB
      2021-07-14 14:57:12   notice : The logging of notice messages has been enabled.
      2021-07-14 14:57:12   notice : Using up to 129.57MiB of memory for query classifier cache
      2021-07-14 14:57:12   notice : syslog logging is enabled.
      2021-07-14 14:57:12   notice : maxlog logging is enabled.
      2021-07-14 14:57:12   notice : Running OS: Linux@5.3.18-24.67-default, #1 SMP Tue Jun 1 14:07:53 UTC 2021 (f0fe006), x86
      _64 with 1 processor cores.
      2021-07-14 14:57:12   notice : Total usable main memory: 863.78MiB.
      2021-07-14 14:57:12   notice : MariaDB MaxScale 2.5.13 started (Commit: d1e1cdec7e3ac58566883dd9d2aebc6c69436455)
      2021-07-14 14:57:12   notice : MaxScale is running in process 16569
      2021-07-14 14:57:12   notice : Configuration file: /etc/maxscale.cnf
      2021-07-14 14:57:12   notice : Log directory: /var/log/maxscale
      2021-07-14 14:57:12   notice : Data directory: /var/lib/maxscale
      2021-07-14 14:57:12   notice : Module directory: /usr/lib64/maxscale
      2021-07-14 14:57:12   notice : Service cache: /var/cache/maxscale
      2021-07-14 14:57:12   notice : Working directory: /var/log/maxscale
      2021-07-14 14:57:12   notice : Loaded module qc_sqlite: V1.0.0 from /usr/lib64/maxscale/libqc_sqlite.so
      2021-07-14 14:57:12   notice : Query classification results are cached and reused. Memory used per thread: 129.57MiB
      2021-07-14 14:57:12   notice : Password encryption key file '/var/lib/maxscale/.secrets' not found, using configured pas
      swords as plaintext.
      2021-07-14 14:57:12   notice : MaxScale started with 1 worker threads, each with a stack size of 8388608 bytes.
      2021-07-14 14:57:12   notice : Loading /etc/maxscale.cnf.
      2021-07-14 14:57:12   notice : /etc/maxscale.cnf.d does not exist, not reading.
      2021-07-14 14:57:12   notice : Loaded module mariadbclient: V1.1.0 from /usr/lib64/maxscale/libmariadbclient.so
      2021-07-14 14:57:12   notice : Loaded module readconnroute: V2.0.0 from /usr/lib64/maxscale/libreadconnroute.so
      2021-07-14 14:57:12   notice : (Standard-Listener) Loaded module MariaDBAuth: V2.1.0 from /usr/lib64/maxscale/libmariadb
      auth.so
      2021-07-14 14:57:12   warning: The MaxScale GUI is enabled but encryption for the REST API is not enabled, the GUI will 
      not be enabled. Configure `admin_ssl_key` and `admin_ssl_cert` to enable HTTPS or add `admin_secure_gui=false` to allow 
      use of the GUI without encryption.
      2021-07-14 14:57:12   notice : Started REST API on [127.0.0.1]:8989
      2021-07-14 14:57:12   notice : Starting a total of 1 services...
      2021-07-14 14:57:12   notice : (Standard-Listener) Listening for connections at [0.0.0.0]:3306
      2021-07-14 14:57:12   notice : Service 'Standard' started (1/1)
      

      tcpdump auf DB-Server sagt: keine Kontaktaufname durch maxscale
      tcpdump auf maxscale-Server sagt. kein Kontaktversuch zum DB-Server
      Versuche mit telnet zu Port 3306 werden erkannt.

      Mit Maxscale 2.4 und obiger Konfig geht alles.

      -> kein Ansatzpunkt

      -----------
      translation:
      since upgrade from maxscale 2.4 to 2.5 maxscale does not connect the database server. We reduced the configuration to minimum (maxscale.cnf):


      see above


      however maxctrl says: Server Down
      no error in the maxscale log, see above

      wie applied tcpdump on both maxscale server an database server: not even an attempt to connect the database server. telnet from maxscale server to database server on the given port is working as expected and recognised by tcpdump

      we downgraded to 2.4: maxscale is working as expected.
      ---------------------------------------------

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            thiesmeincke Thies Meincke
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration