[MXS-2525] before upgrade to 2.3, all works well ,after upgrade maxscale to 2.3.7，some programing drivers can not work well Created: 2019-05-29  Updated: 2020-08-24  Resolved: 2019-05-31

Status: Closed
Project: MariaDB MaxScale
Component/s: Protocol
Affects Version/s: 2.2.1, 2.3.5
Fix Version/s: 2.2.22, 2.3.8

Type: Bug Priority: Major
Reporter: xqzt Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Attachments: PNG File image-2019-05-29-16-11-58-689.png     PNG File image-2019-05-29-16-13-28-344.png     PNG File screenshot-1.png     PNG File screenshot-2.png    

 Description   

mysql 5.7 client work ok as follows

mysql 5.1 client not work well

harbor 1.3 which write in go , report error as follows

####
May 25 11:37:27 172.20.0.1 jobservice[785]: 2019-05-25T03:37:27Z [FATAL] [main.go:41]: failed to initialize database: register db Ping `default`, This server only supports the insecure old password authentication. If you still want to use it, please add 'allowOldPasswords=1' to your DSN. See also https://github.com/go-sql-driver/mysql/wiki/old_passwords
May 25 11:37:27 172.20.0.1 jobservice[785]: [ORM]register db Ping `default`, This server only supports the insecure old password authentication. If you still want to use it, please add 'allowOldPasswords=1' to your DSN. See also https://github.com/go-sql-driver/mysql/wiki/old_passwords
####
*

php report as follows*

Failed to issue SQL query: query = SET NAMES 'utf8' COLLATE 'utf8_unicode_ci', mysql_error = Bad handshake, mysql_errno = 1045.

node report as follows

MySQL server is requesting the old and insecure pre-4.1 auth mechanism.Upgrade the user password or use the

{insecureAuth: true}

option

Other tools

 Comments   
Comment by xqzt [ 2019-05-29 ]

all mysql servers behind maxscale are mysql 5.7.23
maxscale version 2.3.7

Comment by xqzt [ 2019-05-29 ]

tcpdump

Comment by xqzt [ 2019-05-29 ]

[maxscale]
threads=auto

[server1]
type=server
address=10.21.25.201
port=3306
protocol=MariaDBBackend
serv_weight=4

[server2]
type=server
address=10.21.25.202
port=3306
protocol=MariaDBBackend
serv_weight=4

[server3]
type=server
address=10.21.25.203
port=3306
protocol=MariaDBBackend
serv_weight=4

[MariaDB-Monitor]
type=monitor
module=mariadbmon
servers=server1, server2, server3
user=maxscale
password=ourpassword
monitor_interval=1000
detect_replication_lag=true
script=/usr/local/bin/mail_to_admin.sh initiator=$INITIATOR event=$EVENT live_nodes=$NODELIST origin_nodes=$LIST live_master=$MASTERLIST live_slave=$SLAVELIST
events=master_down,slave_down,master_up,slave_up,server_down,server_up,lost_master,lost_slave,new_master,new_slave

[Read-Only-Service]
type=service
router=readconnroute
servers=server1, server2, server3
user=maxscale
password=ourpassword
router_options=slave

[Read-Write-Service]
type=service
router=readwritesplit
servers=server1, server2, server3
user=maxscale
password=ourpassword
max_slave_replication_lag=1
master_accept_reads=true
strict_multi_stmt=true
strict_sp_calls=true

enable_root_user=true
weightby=serv_weight
log_auth_warnings=true
version_string=5.7.23-MariaDB-RWsplit

[MaxAdmin-Service]
type=service
router=cli

[Read-Only-Listener]
type=listener
service=Read-Only-Service
protocol=MariaDBClient
port=4008

[Read-Write-Listener]
type=listener
service=Read-Write-Service
protocol=MariaDBClient
port=3306
address=0.0.0.0

[MaxAdmin-Listener]
type=listener
service=MaxAdmin-Service
protocol=maxscaled
socket=default

Comment by markus makela [ 2019-05-29 ]

Managed to reproduce with the 5.1 client.

Comment by markus makela [ 2019-05-29 ]

What version of MaxScale did you use before?

Comment by markus makela [ 2019-05-29 ]

Looks like this is a bug introduced in a recent 2.2 version.

Comment by markus makela [ 2019-05-29 ]

The bug was introduced into MaxScale 2.2.21 and 2.3.5 so using 2.2.20 or 2.3.4 is a workaround.

Comment by xqzt [ 2019-05-30 ]

I roll back to MaxScale 2.3.4, it works now . Thanks a lot !

Generated at Thu Feb 08 04:14:46 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.