Bug #27677 5.0 Slave Error in Log_event::read_log_event(): message needs to include RBR
Submitted: 5 Apr 2007 20:13 Modified: 4 Sep 2007 11:22
Reporter: Jonathan Miller Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.0 OS:Linux (32 Bit)
Assigned to: Lars Thalmann CPU Architecture:Any

[5 Apr 2007 20:13] Jonathan Miller
When running a 5.1 Master running RBR against a 5.0 Slave (which is not supported) you recieve the following error message:

070405 21:58:42 [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 49, event_type: 19
070405 21:58:42 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error
070405 21:58: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

How to repeat:
See above

Using: replication_UD_frmwrk

Update ud.conf to the following

# The directories the builds will be installed into




#Storage Egnines

Suggested fix:
We should add verbage that talks about a newer master running RBR as one of the possible issues.
[4 Sep 2007 11:22] Lars Thalmann
The error message says that the event is invalid.  And it is so for a
5.0 server.  I don't see why this would be a bug.