5 messages in com.mysql.lists.mysqlRe: Client being locked out by aborte...
FromSent OnAttachments
Bill Moran24 Oct 2006 08:22 
Dan Buettner24 Oct 2006 08:48 
Bill Moran24 Oct 2006 10:07 
Bill Moran26 Oct 2006 10:42 
Dan Buettner26 Oct 2006 11:36 
Subject:Re: Client being locked out by aborted connections
From:Dan Buettner (drbu@gmail.com)
Date:10/24/2006 08:48:34 AM
List:com.mysql.lists.mysql

Bill, you can up the value of 'max_connect_errors' (default is 10 it appears) to make this problem appear less frequently while you troubleshoot.

See more information at: http://dev.mysql.com/doc/refman/5.0/en/blocked-host.html http://dev.mysql.com/doc/refman/5.0/en/communication-errors.html

As you'll see from above - Could be a bad username and password from your PHP app (should it really be connecting as root?), PHP not closing connection, bad hardware, network problems, etc. If it coincides with a system upgrade, what exactly was upgraded?

Dan

On 10/24/06, Bill Moran <wmo@collaborativefusion.com> wrote:

I have a problem with a PHP client that is frequently getting locked out by the following errors: 061020 14:57:25 [Warning] Aborted connection 7 to db: 'dbname' user: 'root'
host: `hostname.collaborativefusion.com' (Got an error reading communication
packets)

About once a day, the PHP application becomes unable to contact the database and we get an error suggesting that we use "mysqladmin flush-hosts". This re-enables the connection, until it happens again. I'd like to actually _fix_ the problem, but I need to keep the application available until then.

I'm interested in help on 2 fronts: 1) If anyone can tell me why PHP suddenly started causing these errors and how to make it stop, I'd be interested to hear. I've already tried turning off persistent connections to no avail. 2) Until I can diagnose and fix the real cause of the problem, how can I configure the MySQL server _not_ to disable connections as a result of connection aborts?

Details: First off, the appearance of this problem coincides with a large system upgrade, so it's obviously something new either in PHP or MySQL. Client: FreeBSD 5.3-RELEASE-p37 php5-pgsql-5.1.6_1 mysql-client-4.1.21 Server: FreeBSD 5.3-RELEASE-p37 mysql-server-4.1.21