I appreciate the response, but this is not the issue (verified by running "SHOW STATUS", which shows the "Threads_connected" counter). MySQL has a parameter called "max_connect_errors" that defaults to ten. If a host reaches the value of "max_connect_errors" then MySQL will drop further connections from that host without allowing authentication.
Essentially the "max_connect_errors" parameter exists to keep malfunctioning clients from causing more harm to a MySQL server. When Zenoss connects to a MySQL server and disconnects it is seen as a malfunctioning client. MySQL does the right thing and drops future connections from that host. This should only cause problems if the server on which Zenoss is running would need to connect to the MySQL server for some reason other than monitoring. Even after "max_connect_errors" is reached, a connection to the MySQL server works; it is just dropped immediately. So as far as Zenoss is concerned MySQL is still up and running. But if any other process on the same server needed to connect to the MySQL server it would not be able to. ------------------------ Mike -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=11232#11232 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
