Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.0.3, 2.0.4
-
None
-
CentOS 6.8
2.6.32-642.13.1.el6.x86_64
Description
We use maxadmin to monitor the status of our database servers.
For example, if server A is indeed being used as Master and all others are Slave and are Synced.
In MaxScale 1.4.3 this went well. But since we've upgraded to 2.0.3 (and 2.0.4 today), every now and then the output of maxadmin is: "Could not read password prompt from MaxScale."
And we get an alert from our monitoring system.
Our command (password removed):
maxadmin -p******** 'list servers'
|
Servers.
|
-------------------+-----------------+-------+-------------+--------------------
|
Server | Address | Port | Connections | Status
|
-------------------+-----------------+-------+-------------+--------------------
|
db-03 | 192.168.120.74 | 3306 | 17 | Master, Synced, Running
|
db-04 | 192.168.120.95 | 3306 | 3 | Slave, Synced, Running
|
db-05 | 192.168.120.96 | 3306 | 3 | Slave, Synced, Running
|
db-06 | 192.168.120.97 | 3306 | 3 | Slave, Synced, Running
|
db-07 | 192.168.120.98 | 3306 | 3 | Slave, Synced, Running
|
db-08 | 192.168.120.99 | 3306 | 2 | Slave, Synced, Running
|
db-09 | 192.168.120.100 | 3306 | 3 | Slave, Synced, Running
|
-------------------+-----------------+-------+-------------+--------------------
|
|
It can be reproduced by running this command in a for loop:
for i in {1..100}; do maxadmin -p******** 'list servers' | egrep -v 'db|Server|^-'; done
|
Could not read password prompt from MaxScale.
|