Bug #58729 Could not able to read log_event correctly - sanity check

• Submitted: 4 Dec 2010 9:20
• Modified: 4 Dec 2010 20:01
• Reporter: Anil Alpati
• Status: Not a Bug
• Category: MySQL Server
• Severity: S1 (Critical)
• Version: 5.1.45
• OS: Any
• CPU Architecture: Any

[4 Dec 2010 9:20] Anil Alpati

Description:
Sanity check failed - could not able to read log_event

How to repeat:

F:\MifosReplication\EOM3308\bin>mysqlbinlog F:\MifosReplication\Adminfiles\Incre
mentalbackupfiles\BackupFiles\MIFO_Incr.000741 | mysql --user=root --password=db
admin@permgfs123 --port=3308 2>> F:\MifosReplication\Adminfiles\Incrementalbacku
pfiles\BackupFiles\errorlog.txt
ERROR: Error in Log_event::read_log_event(): 'Sanity check failed', data_len: 10
1, event_type: 120
ERROR: Could not read entry at offset 19972366: Error in log format or read erro
r.

F:\MifosReplication\EOM3308\bin>mysqlbinlog --verbose F:\MifosReplication\Adminf
iles\Incrementalbackupfiles\BackupFiles\MIFO_Incr.000741 > F:\MifosReplication\A
dminfiles\Incrementalbackupfiles\BackupFiles\741.txt
ERROR: Error in Log_event::read_log_event(): 'Sanity check failed', data_len: 10
1, event_type: 120
ERROR: Could not read entry at offset 19972366: Error in log format or read erro
r.

[4 Dec 2010 9:23] Anil Alpati

Even in verbose - could not able to extract the binlog file.

How can i fix this ?

Kindly reply at your earliest.

[4 Dec 2010 10:00] Anil Alpati

Fixed the issue.. found out log event = mapped the position accordingly. Since bytes data is sending huge bytes..

its working now ...

[4 Dec 2010 20:01] MySQL Verification Team

According last comment.