[MXS-3910] Could not manage the replication instance of binlog router Created: 2021-12-13  Updated: 2022-02-24  Resolved: 2022-02-24

Status: Closed
Project: MariaDB MaxScale
Component/s: binlogrouter
Affects Version/s: 2.4.17
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Michael Liu Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Environment:

NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"


 Description   

Several months ago, I use mariadb maxscale built a binlog router for backup mysql binlog. At the beginning, everything was good.
Today I found one of the instance could not be logged in. The error said my password is incorrect.
However, I use the same password that I record to login into the other replication instance, it login succussfully.
(I only setted two replication instance, and both of them use the same use and password to connect the source mysql instance and manage themselves).
I also use the same use and password to login into the source instances, it works good.
After that, I check the master.ini config in datadir, the user and password also not changed.
I think this may be a bug, please help!

Here is my config.

cat /etc/maxscale.cnf
 
 
 
[maxscale]
 
threads=auto
 
logdir=/data/maxscale/logs
 
datadir=/data/maxscale/data
 
cachedir=/data/maxscale/cache
 
execdir=/data/maxscale/exec
 
persistdir=/data/maxscale/persist
 
 
 
[Replication1]
 
type=service
 
router=binlogrouter
 
user=repl
 
password=57FFB3A814B198622160312A241D447DBD86459C5BCDA333CBA4BD4F86DEA7D9
 
server_id=185301
 
slave_hostname=172.16.0.18
 
binlogdir=/data/maxscale/binlog/tencent_biz
 
transaction_safety=1
 
heartbeat=30
 
send_slave_heartbeat=1
 
semisync=0
 
mariadb10-compatibility=0
 
 
 
[Replication2]
 
type=service
 
router=binlogrouter
 
user=repl
 
password=57FFB3A814B198622160312A241D447DBD86459C5BCDA333CBA4BD4F86DEA7D9
 
server_id=185302
 
slave_hostname=172.16.0.18
 
binlogdir=/data/maxscale/binlog/tencent_biz_divedb
 
transaction_safety=1
 
heartbeat=30
 
send_slave_heartbeat=1
 
semisync=0
 
mariadb10-compatibility=0
 
 
 
[Replication-Listener1]
 
type=listener
 
service=Replication1
 
protocol=MySQLClient
 
port=5301
 
 
 
[Replication-Listener2]
 
type=listener
 
service=Replication2
 
protocol=MySQLClient
 
port=5302
 
 
 
[MaxAdminService]
 
type=service
 
router=cli
 
 
 
[MaxAdminUnixListener]
 
type=listener
 
service=MaxAdminService
 
protocol=maxscaled
 
socket=default
 
 
 
[MaxAdminInetListener]
 
type=listener
 
service=MaxAdminService
 
protocol=maxscaled
 
address=localhost
 
port=5400

I try to log into Replication1, it works good.
I try to log into Replication2, it works bad.

 Comments   
Comment by Johan Wikman [ 2021-12-13 ]

Could you please write the description in English. Unfortunately we are not fluent in Chinese.
Johan

Comment by Michael Liu [ 2021-12-13 ]

updated

Comment by markus makela [ 2022-01-04 ]

michael-liumh have you tested if this happens in 2.5?

Comment by Michael Liu [ 2022-01-08 ]

maxscale 2.5 binlogrouter is different from 2.4, it's not my option.

Comment by Michael Liu [ 2022-01-08 ]

https://mariadb.com/kb/en/mariadb-maxscale-25-binlogrouter/

NOTE: The binlog router delivered with 2.5 is completely new and is not 100% backward compatible with the binlog router delivered with earlier versions of MaxScale.

Comment by Michael Liu [ 2022-02-11 ]

I found the solution that I need to use slave_hostname to connect instance instead of use 127.0.0.1.

Comment by markus makela [ 2022-02-24 ]

I'm assuming this means the problem is no longer present.

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