[MXS-3975] Authentication failed on binlogrouter service Created: 2022-02-01  Updated: 2022-03-23  Resolved: 2022-03-23

Status: Closed
Project: MariaDB MaxScale
Component/s: binlogrouter
Affects Version/s: 2.5.16, 2.5.18
Fix Version/s: N/A

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

CentOS Stream 8



 Description   

Have simple config

[db_11]
type=server
address=172.16.13.9
port=3306
protocol=MariaDBBackend
 
[db_12]
type=server
address=172.16.12.5
port=3306
protocol=MariaDBBackend
 
[MariaDB-Monitor]
type=monitor
module=mariadbmon
servers=db_11,db_12
user=maxscale_user
password=maxscale_pass
monitor_interval=2s
auto_failover=false
auto_rejoin=false
 
[Replication-Proxy]
type=service
router=binlogrouter
cluster=MariaDB-Monitor
select_master=true
expire_log_duration=5h
expire_log_minimum_files=3
user=maxscale_user
password=maxscale_pass
 
[Replication-Listener]
type=listener
service=Replication-Proxy
protocol=MariaDBClient
port=3303

Log:

2022-02-01 23:21:02   notice : The systemd watchdog is Enabled. Internal timeout = 30s
2022-02-01 23:21:02   notice : Worker message queue size: 1MiB
2022-02-01 23:21:02   notice : Using up to 18.77GiB of memory for query classifier cache
2022-02-01 23:21:02   notice : syslog logging is enabled.
2022-02-01 23:21:02   notice : maxlog logging is enabled.
2022-02-01 23:21:02   notice : Running OS: Linux@4.18.0-358.el8.x86_64, #1 SMP Mon Jan 10 13:11:20 UTC 2022, x86_64 with 40 processor cores.
2022-02-01 23:21:02   notice : Total usable main memory: 125.14GiB.
2022-02-01 23:21:02   notice : MariaDB MaxScale 2.5.16 started (Commit: 34282097d0d149abb22c4d272da1da47415eb775)
2022-02-01 23:21:02   notice : MaxScale is running in process 245268
2022-02-01 23:21:02   notice : Configuration file: /etc/maxscale.cnf
2022-02-01 23:21:02   notice : Log directory: /var/log/maxscale
2022-02-01 23:21:02   notice : Data directory: /var/lib/maxscale
2022-02-01 23:21:02   notice : Module directory: /usr/lib64/maxscale
2022-02-01 23:21:02   notice : Service cache: /var/cache/maxscale
2022-02-01 23:21:02   notice : Working directory: /var/log/maxscale
2022-02-01 23:21:02   notice : Loaded module qc_sqlite: V1.0.0 from /usr/lib64/maxscale/libqc_sqlite.so
2022-02-01 23:21:02   notice : Query classification results are cached and reused. Memory used per thread: 480.55MiB
2022-02-01 23:21:02   notice : Password encryption key file '/var/lib/maxscale/.secrets' not found, using configured passwords as plaintext.
2022-02-01 23:21:02   notice : MaxScale started with 40 worker threads, each with a stack size of 8388608 bytes.
2022-02-01 23:21:02   notice : Loading /etc/maxscale.cnf.
2022-02-01 23:21:02   notice : /etc/maxscale.cnf.d does not exist, not reading.
2022-02-01 23:21:02   notice : Loaded module MariaDBClient: V1.1.0 from /usr/lib64/maxscale/libmariadbclient.so
2022-02-01 23:21:02   notice : Loaded module binlogrouter: V1.0.0 from /usr/lib64/maxscale/libbinlogrouter.so
2022-02-01 23:21:02   notice : Loaded module mariadbmon: V1.5.0 from /usr/lib64/maxscale/libmariadbmon.so
2022-02-01 23:21:02   warning: (Replication-Proxy) No (replication) master found. Retrying silently until one is found.
2022-02-01 23:21:02   notice : (Replication-Listener) Loaded module MariaDBAuth: V2.1.0 from /usr/lib64/maxscale/libmariadbauth.so
2022-02-01 23:21:02   notice : Started REST API on [0.0.0.0]:8989
2022-02-01 23:21:02   notice : 'db_12' sent version string '10.4.22-MariaDB-log'. Detected type: 'MariaDB', version: 10.4.22.
2022-02-01 23:21:02   notice : 'db_11' sent version string '10.4.15-MariaDB-log'. Detected type: 'MariaDB', version: 10.4.15.
2022-02-01 23:21:02   notice : Server 'db_12' charset: latin1
2022-02-01 23:21:02   notice : Server 'db_11' charset: latin1
2022-02-01 23:21:02   notice : Starting a total of 1 services...
2022-02-01 23:21:02   notice : (Replication-Listener) Listening for connections at [::]:3303
2022-02-01 23:21:02   notice : Service 'Replication-Proxy' started (1/1)
2022-02-01 23:21:03   notice : Read 28 user@host entries from 'db_11' for service 'Replication-Proxy'.
2022-02-01 23:21:12   error  : (Replication-Proxy) Error received during replication from '172.16.13.9:3306': Failed to fetch binlog event from master: Could not find GTID state requested by slave in any binlog files. Probably the slave state is too old and required binlog files have been purged.

OK, need change GTID
trying (172.16.116.20 - IP Maxscale server):
mysql -umaxscale_user -pmaxscale_pass -h172.16.116.20 -P3303
ERROR 1045 (28000): Access denied for user 'maxscale_user'@'::ffff:172.16.116.20' (using password: YES)
From other hosts the situation is the same (Access denied)
Check 2.5.18 version - is the same
Reset master can't do.
Monitor is working good.



 Comments   
Comment by markus makela [ 2022-02-02 ]

Does the maxscale_user have the host defined as % or as a specific IP address?

Comment by Streltsov [ 2022-02-02 ]

In db_11/db_12 created user maxscale_user@%
I tried to specify different hosts to the user
and monitor use this user and connected without problem

Comment by markus makela [ 2022-02-24 ]

Does maxctrl show dbusers Replication-Proxy return the correct set of users?

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