Talk:Question:mysqladmin host blocked because of many connection errors

Edit

Possible causes of too many connections

Mjoseph 16:31, 11 October 2005 (PDT)

You can also check for an application not properly closing database connections. In one instance, we had Tomcat configured to use persistent connections. However, each request initiated a new connection due to our incorrect configuration.

You can use 
 mysqladmin -u <user> -p<password> processlist
to see a list of current connections.


Edit

Improved behavior in MySQL 5.1

WombatNation 13:19, 05 April 2008 (PDT)

In MySQL 5.1, the connection error tracking behavior was changed so that a successful connection from a host resets the connection error counter back to zero for that host. This is a big improvement if you have a server with a really long uptime and you have clients connecting from hosts with intermittent connection issues. If you use the default setting with MySQL 5.0 and earlier, a client could be locked out even if errors rarely occur, simply because the error count reached 10 for that host over the long uptime for the server (or long period of time between running the flush hosts command).

The new behavior in MySQL 5.1 generally allows you to keep the `max_connect_errors' system variable low, thus hopefully achieving the original purpose of helping protect your database server from direct connections from hostile hosts.

On the other hand, the new behavior could be hiding intermittent connection error issues that you might want to know about and fix. But, nothing is stopping you from setting the count lower than 10.

MediaWiki

This page has been accessed 1,584 times.

This page was last modified 19:56, 5 April 2008.