Thx's :)
David Griffiths wrote:
These errors could mean a connection timed out, or a mysql-client didn't
properly close the connection, or possibly a network error.
I went to mysql.com and looked in the searchable docs:
http://dev.mysql.com/doc/mysql/en/Communication_errors.html
These errors could mean a connection timed out, or a mysql-client didn't
properly close the connection, or possibly a network error.
I went to mysql.com and looked in the searchable docs:
http://dev.mysql.com/doc/mysql/en/Communication_errors.html
If |Aborted connections|
Hello,
I recently noticed this error in our mysql error log file:
Aborted connection 5439 to db: 'database_name' user: 'someuser' host:
`localhost' (Got an error reading communication packets)
-
On Tuesday 03 April 2001 17:12, Jean-Luc Fontaine wrote:
> On my replicated linux machines with the latest 3.23.36 rpm from mysql.com,
> I have been getting the following errors lately:
>
> 010403 17:08:35 Slave: received 0 length packet from server, apparent
> master shutdown: (0)
> 010403 17:0
On my replicated linux machines with the latest 3.23.36 rpm from mysql.com, I
have been getting the following errors lately:
010403 17:08:35 Slave: received 0 length packet from server, apparent master
shutdown: (0)
010403 17:08:35 Slave: Failed reading log event, reconnecting to retry, log
