Bug #69791 Got an error writing communication packets
Submitted: 19 Jul 2013 10:38 Modified: 28 Jul 2013 1:55
Reporter: jason bell Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.5.32 OS:Linux
Assigned to: CPU Architecture:Any
Tags: Got an error writing communication packets

[19 Jul 2013 10:38] jason bell
my situation is almost the same with bug below,

since the server is updated from 5.1 to 5.5,
the "Got an error writing communication packets" occurred randomly.

let me describe the status of server in detail,there are two database A and B in the server(running in SunOS),A has federal table,B don't. but B still have error.And the web work is just fine.because if you run this program latter,the error cannot appear.sometime this error happens serveral times,and sometimes it just disappear for serveral days.
  Is there any relation with the federal table?
please help me to find the reason.
if you want any more information please just say your request,i will add it later.

thank you.

How to repeat:
Unable to repeat it. It appears randomly after some hour using it
[28 Jul 2013 1:55] MySQL Verification Team
Thank you for the bug report. Please re-open this bug report when you are able to provide a repeatable test case. Thanks.
[17 Sep 2013 14:48] Dan Kennedy
IS this not a duplicate of 66184 (http://bugs.mysql.com/bug.php?id=66184)
[11 Oct 2013 1:28] Justin Xu
I met the same problem too after I upgrade MySQL 5.5 to 5.5.32 and 5.5.33.
OS: Solaris 10 .
I use Federated table in the database,but when applications access the MyISAM tables ,the applications often report the error message like "****************************************************************************************
2013-10-10 05:45:07,009 [Thread-12      ] WARN  ExceptionLogger                - When insert records, can not connect to db or the table is locked. error code:1160 sql state:08S01 table name:nofruit2013 error msg:Got an error writing communication packets
I upgrade Mysql 5.5.32 to 5.5.33 ,but the error message still appears.