mmm agent cannot connect to MySQL even when mmm agent user is already created on DB

Bug #794500 reported by Gurvinder Dadyala
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I have made 2 DB nodes, 1 monitor node and i have 2 virtual IPs [,]. When i start mmm-monitor on monitor node and other agents on DB nodes everything works well. MMM-monitor assigns writer role to DB1 and reader role to DB2. After 15 or 30 mins mmm-agent on assigned writer node starts throwing error message that it is not able to connect to MySQL. I am not sure why it does so because mmm-agent user is already created under both db nodes and mmm-agent does not throw this message when you start agents. It happens in between automatically after 15-30 mins. Following is the error message.

2011/06/08 14:01:16 FATAL Couldn't deny writes: ERROR: Can't connect to MySQL (host =, user = mmm_agent)! Can't connect to MySQL server on '' (4)

I have checked configuration files on both nodes and everything is good. Even i have deleted user credentials and created them again just to make sure it is not because of mmm-agent user credentials. This usually happens on node which has been assigned writer role. There is no fixed time for this error message. I am able to connect to both nodes after i start monitor and other agents. Agent DB with assigned writer role automatically starts throwing error that agent is not able to to MySQL and then after 5-6 min it works fine. I want to know is this a bug or something else is not right

tags: added: mysql-mmm
removed: mysql-mm
Revision history for this message
Kenny Gryp (gryp) wrote :

The errorcode 4 is mentioned in your error.
This means that the code got interrupted, which indicates a timeout during the checks.

You might want to investigate connection time to mysql. or higher the timeout for the checks.

Revision history for this message
Slava (slava-tangramltd) wrote :

Try from monitor node connect to mysql.
And check DNS, if have delay.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers