tigerpaws
2012-01-25 18:37:41 UTC
tigerpaws [http://community.zenoss.org/people/tigerpaws] created the discussion
"Mysql connection errors stop the monitoring"
To view the discussion, visit: http://community.zenoss.org/message/63915#63915
--------------------------------------------------------------
On many of my servers monitored by zenoss, I get the "Host '...' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'" alert. Yet, if I reset mysql, everything is fine for a while, so there are no connection errors. What kind of connection errors could I be getting to cause mysql to blacklist the zenoss system? The logon timeouts for the MySQL module are at 15 seconds, which seems more than ample. Yet I get this from nearly all my servers where mysql is being monitored. There is no mention of this in the mysql log. This really messes up the monitoring and leaves large holes in the graphs.
Does anyone have any idea how to test this to find out exactly what is causing these errors?
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/63915#63915]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Mysql connection errors stop the monitoring"
To view the discussion, visit: http://community.zenoss.org/message/63915#63915
--------------------------------------------------------------
On many of my servers monitored by zenoss, I get the "Host '...' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'" alert. Yet, if I reset mysql, everything is fine for a while, so there are no connection errors. What kind of connection errors could I be getting to cause mysql to blacklist the zenoss system? The logon timeouts for the MySQL module are at 15 seconds, which seems more than ample. Yet I get this from nearly all my servers where mysql is being monitored. There is no mention of this in the mysql log. This really messes up the monitoring and leaves large holes in the graphs.
Does anyone have any idea how to test this to find out exactly what is causing these errors?
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/63915#63915]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]