Bug #56635 Error Whille restoring binlog in slave server
Submitted: 8 Sep 2010 5:04 Modified: 8 Oct 2010 6:50
Reporter: Anil Alpati Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.1 OS:Any
Assigned to: CPU Architecture:Any

[8 Sep 2010 5:04] Anil Alpati 
Description:

The Below Error which i'm getting while restoring binlog file using mysqlbinlog command

ERROR: Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 7567104, event_type: 0
ERROR: Could not read entry at offset 18268427: Error in log format or read error.

Please revert at your earliest.

How to repeat:

The Below Error which i'm getting while restoring binlog file using mysqlbinlog command

ERROR: Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 7567104, event_type: 0
ERROR: Could not read entry at offset 18268427: Error in log format or read error.

Please revert at your earliest.
[8 Sep 2010 6:50] Valeriy Kravchuk 
What exact server version, 5.1.x, do you have on master and on slave? Do you have any unusual messages at OS level logs? Can you upload problematic binary log (compressed)?
[8 Oct 2010 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".