chusiang / mysql-master-master

Automatically exported from code.google.com/p/mysql-master-master
GNU General Public License v2.0
1 stars 1 forks source link

mmm agent automatically starts showing not able connect mysql intermittently #54

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
I have already setup mmm agent user in both MySQL nodes still it shows mmm 
agent is not able to connect to mysql. This error does not come up when i start 
agent. This happens after 15-20 min and then after 2-3 mins it gets fixed 
automatically
Error message is as follows
2011/06/09 13:55:23  INFO We have some new roles added or old rules deleted!
2011/06/09 13:55:23  INFO Added:   reader(192.168.100.197), 
writer(192.168.100.196)
2011/06/09 13:56:06  INFO We have some new roles added or old rules deleted!
2011/06/09 13:56:06  INFO Deleted: reader(192.168.100.197)
2011/06/09 14:42:50 FATAL Couldn't allow writes: ERROR: Can't connect to MySQL 
(host = 192.168.100.98:3306, user = mmm_agent)! Can't connect to MySQL server 
on '192.168.100.98' (4)
2011/06/09 14:49:14 FATAL Couldn't allow writes: ERROR: Can't connect to MySQL 
(host = 192.168.100.98:3306, user = mmm_agent)! Can't connect to MySQL server 
on '192.168.100.98' (4)
2011/06/09 14:51:26 FATAL Couldn't allow writes: ERROR: Can't connect to MySQL 
(host = 192.168.100.98:3306, user = mmm_agent)! Can't connect to MySQL server 
on '192.168.100.98' (4)
2011/06/09 14:54:50 FATAL Couldn't allow writes: ERROR: Can't connect to MySQL 
(host = 192.168.100.98:3306, user = mmm_agent)! Can't connect to MySQL server 
on '192.168.100.98' (4)

What is the expected output? What do you see instead?
mmm agent should not throw this message when mmm agent user is already 
configured in MySQL

What version of the product are you using? On what operating system?
MMM 2.2.1
Linux centos03 2.6.18-238.el5 #1 SMP Thu Jan 13 16:24:47 EST 2011 i686 i686 
i386 GNU/Linux

Please provide any additional information below.

Original issue reported on code.google.com by gsd2...@gmail.com on 9 Jun 2011 at 9:39