Page 1 of 1

weird problem with mysql - Got an error reading communicatio

Posted: Thu Mar 21, 2013 3:18 pm
by nobody
Hello,

I am getting some very worrying erros that I don't know what they are. I googled around and found that some say it has do something with the OS recv... I don't know what the problem is though. I have never come across that in the past.
Plesk backup isn't also able to complete a specific database dumps that has these errors so I am very worried.
I tried repairing and optimizing all databases - restarting mysql but this didn't solve the problem.
To be honest this started after the last updated I pushed.
Does anyone else have the same issue ?

Code: Select all

130319  1:19:20 [Warning] Aborted connection 433780 to db: 'psa' user: 'admin' host: 'localhost' (Got an error reading communication packets)
130321  4:32:26 [Warning] Aborted connection 549272 to db: 'sitebuilder5' user: 'pp_sb_db' host: 'localhost' (Got timeout reading communication packets)
130320  4:54:40 [Warning] Aborted connection 501807 to db: 'some_customer_db' user: 'some_user' host: 'localhost' (Got an error reading communication packets)

mysql-server 5.5.30-15.el5.art
kernel 2.6.32.60-36.art.x86_64

Re: weird problem with mysql - Got an error reading communic

Posted: Thu Mar 21, 2013 3:23 pm
by prupert
See http://dev.mysql.com/doc/refman/5.5/en/ ... rrors.html for more information about this error.

The reason that you only just see it being logged now is probably because you had not set "log-warnings=2" in the my.cnf before. ASL has started reporting this as a vulnerability since a couple of releases and just recently also fixes this my.cnf option for you after running "asl s -f". See http://dev.mysql.com/doc/refman/5.5/en/ ... g-warnings as well.

Re: weird problem with mysql - Got an error reading communic

Posted: Thu Mar 21, 2013 3:29 pm
by mikeshinn
ASL has started reporting this as a vulnerability since a couple of releases and just recently also fixes this my.cnf option for you after running "asl s -f".
Thats correct. Thats also the only way to detect a login failure for mysql. Surprisingly, this is not logged by default, so if someone is brute forcing mysql, you wouldnt have known.