Bug #27498 Error reading packet from server:
Submitted: 28 Mar 2007 13:20 Modified: 28 Apr 2007 13:33
Reporter: kris dba Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:5.0.20 OS:Linux (redhat linux)
Assigned to: CPU Architecture:Any
Tags: replication error mysql 5.0.20

[28 Mar 2007 13:20] kris dba
Description:
Hi,
Iam getting the problem in Mysql replication from master to slave.
iam getting this error on every other day and the replication is getting failed..
i need to manually reset the slave..in order to make it sync with master..
It is getting repeated....
see the error log entry...

070320 19:18:42 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 3259584, event_type: 2
070320 19:18:42 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error
070320 19:18:42 [ERROR] Slave: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 0
070320 19:18:42 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db1-bin.000001' position 77679213
070320 19:18:42 [ERROR] Error reading packet from server: Out of memory (Needed 3259592 bytes) ( server_errno=5)
070320 19:18:42 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'db1-bin.000001' position 79383168
070320 19:18:42 [Note] Slave: connected to master 'root@x.x.x.x:3306',replication resumed in log 'db1-bin.000001' at position 79383168
070320 19:18:43 [ERROR] Error reading packet from server: error reading log entry ( server_errno=1236)
070320 19:18:43 [ERROR] Got fatal error 1236: 'error reading log entry' from master when reading data from binary log
070320 19:18:43 [Note] Slave I/O thread exiting, read up to log 'db1-bin.000001', position 79383168

070322  1:58:08 [ERROR] Error reading packet from server: Out of memory (Needed 10060832 bytes) ( server_errno=5)
070322  1:58:08 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'db1-bin.000001' position 59307252
070322  1:58:08 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 10060823, event_type: 2
070322  1:58:08 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error
070322  1:58:08 [ERROR] Slave: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 0
070322  1:58:08 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db1-bin.000001' position 57603297
070322  1:58:08 [Note] Slave: connected to master 'root@x.x.x.x:3306',replication resumed in log 'db1-bin.000001' at position 59307252
070322  1:58:08 [ERROR] Error reading packet from server: Out of memory (Needed 928532344 bytes) ( server_errno=5)

How to repeat:
I have put heavy load on the master server and tested it..its getting repeated..
see the timestamp in the errorlog for more information.
[28 Mar 2007 13:33] MySQL Verification Team
Thank you for the bug report. Could you please test with the latest
released version 5.0.37 and comment the results. Thanks in advance.
[28 Apr 2007 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".