Hello.
Have a look here: http://dev.mysql.com/doc/mysql/en/Communication_errors.html Viktor Fougstedt wrote: > > Hi. > > We have a MySQL database as backend on our 15.000 user mailserver. This > MySQL instance receives a large amount of connections, each performing > just a small amount of processing (a few SELECT:s) before disconnecting. > > Our mysql.err log is filling up with lines like the below: > > 051020 10:50:29 Aborted connection 1023489 to db: 'XXX' user: 'YYY' > host: `ZZZ' (Got an error reading communication packets) > > On an typical day, there are some 600.000 connects to the database, and > about 5.000 of those connection attempts lead to a connect error > (that's almost 1%). If it is the mysql client connecting in these > cases, the error code returned is 2002, but most connects come from > other programs using libmysql. > > Can someone give us a hint what might be lacking in our setup to cause > this behaviour? What can we alter to make this stop happening? > > > Regards, > /Viktor... > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
