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

client gets disconnected when using Maxscale

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Incomplete
    • 23.08.3
    • N/A
    • readwritesplit
    • None

    Description

      hi,
      connection is dropped by MariaDB when using maxscale while all works fine if connecting directly to the db.
      connection is from an Azure VM:
      OS: Windows Server 2022 Datacenter
      MariaDB client: 11.2.2 and also tested with 11.1.4

      Maxscale server:
      MXS version: 23.08.03
      OS: Red Hat Enterprise Linux release 8.9 (Ootpa)

      Database server:
      MariaDB version: 10.11.8-MariaDB-log
      OS: Red Hat Enterprise Linux release 8.9 (Ootpa)

      all MariaDB products are community

      below the log info from maxscale (no error)
      2024-02-12 14:37:02 info : (295) [MariaDBProtocol] Connection attributes: _os=Windows _client_name=libmariadb _pid=10856 _server_host=10.0.90.222 _platform=AMD64 _client_version=3.3.8 program_name=mysql _thread=9748
      2024-02-12 14:37:02 info : (295) Found matching user 'JR007232'@'10.%' for client 'JR007232'@'10.211.0.13' with sufficient privileges.
      2024-02-12 14:37:02 info : (295) [readwritesplit] (SplitterService); Target connection counts:
      2024-02-12 14:37:02 info : (295) [readwritesplit] (SplitterService); current operations : 0 in mariadb1 Master, Running
      2024-02-12 14:37:02 info : (295) [readwritesplit] (SplitterService); current operations : 0 in mariadb2 Slave, Running
      2024-02-12 14:37:02 info : (295) [readwritesplit] (SplitterService); current operations : 0 in mariadb3 Slave, Running
      2024-02-12 14:37:02 info : (295) (mariadb1); Sending proxy-protocol header 'PROXY TCP4 10.211.0.13 10.0.90.223 49881 3306' to server 'mariadb1'.
      2024-02-12 14:37:02 info : (295) [readwritesplit] (SplitterService); Connected to 'mariadb1'
      2024-02-12 14:37:02 info : (295) [readwritesplit] (SplitterService); Selected Primary: mariadb1
      2024-02-12 14:37:02 info : (295) (mariadb2); Sending proxy-protocol header 'PROXY TCP4 10.211.0.13 10.0.90.224 49881 3306' to server 'mariadb2'.
      2024-02-12 14:37:02 info : (295) [readwritesplit] (SplitterService); Connected to 'mariadb2'
      2024-02-12 14:37:02 info : (295) [readwritesplit] (SplitterService); Selected Replica: mariadb2
      2024-02-12 14:37:02 info : (295) (mariadb3); Sending proxy-protocol header 'PROXY TCP4 10.211.0.13 10.0.90.225 49881 3306' to server 'mariadb3'.
      2024-02-12 14:37:02 info : (295) [readwritesplit] (SplitterService); Connected to 'mariadb3'
      2024-02-12 14:37:02 info : (295) [readwritesplit] (SplitterService); Selected Replica: mariadb3
      2024-02-12 14:37:02 info : (295) Started SplitterService client session [295] for 'JR007232' from 10.211.0.13 on 'Worker-03'
      2024-02-12 14:37:02 info : (295) Connected to 'mariadb1' with thread id 24560541
      2024-02-12 14:37:02 info : (295) Connected to 'mariadb3' with thread id 26979114
      2024-02-12 14:37:02 info : (295) Connected to 'mariadb2' with thread id 26979221
      2024-02-12 14:37:02 info : (295) Authentication to 'mariadb1' succeeded.
      2024-02-12 14:37:02 info : (295) Authentication to 'mariadb3' succeeded.
      2024-02-12 14:37:02 info : (295) Authentication to 'mariadb2' succeeded.

      attached is the tcpdump and an audit log image

      After connecting when any command is tried (select,show,etc.) the client gets the following error:
      ERROR 2013 (HY000): Lost connection to server at 'reading authorization packet', system error: 0

      All works fine if Maxscale is bypassed and client connects directly to the db

      Attachments

        Activity

          There are no comments yet on this issue.

          People

            johan.wikman Johan Wikman
            Bongini Luigi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.