[MXS-4115] Maxscale prints user/pass with CHANGE MASTER command in logfile while failover. Created: 2022-04-28  Updated: 2022-06-24  Resolved: 2022-05-17

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: 2.5.19
Fix Version/s: 2.5.21, 6.4.0

Type: Bug Priority: Critical
Reporter: Nilnandan Joshi Assignee: Esa Korhonen
Resolution: Fixed Votes: 1
Labels: None

Sprint: MXS-SPRINT-157

 Description   

maxscale prints complete CHANGE MASTER command in maxscale.log along with username and plain text password while failover. Also, there is no debug=enable-statement-logging set in the [maxscale] section in maxscale.cnf.

2022-04-27 19:02:20   notice : [mariadbmon] Performing automatic failover to replace failed master 'node2'.
2022-04-27 19:02:20   notice : [mariadbmon] Failover 'node2' -> 'node1' performed.
2022-04-27 19:02:20   notice : Server changed state: node1[:6603]: new_master. [Slave, Running] -> [Master, Running]
2022-04-27 19:03:11   notice : Server changed state: node2[:6603]: server_up. [Down] -> [Running]
2022-04-27 19:03:11   notice : [mariadbmon] Directing standalone server 'node2' to replicate from 'node1'.
2022-04-27 19:03:11   warning: [mariadbmon] Query 'SET STATEMENT max_statement_time=10 FOR CHANGE MASTER '' TO MASTER_HOST = '127.0.0.1', MASTER_PORT = 6603, MASTER_USE_GTID = current_pos, MASTER_USER = 'test', MASTER_PASSWORD = 'test@123';' failed on 'node2': 'Lost connection to MySQL server during query' (2013). Retrying with 89.8 seconds left.


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