MySQL Bugs: #2119: mysqlbinlog 'Event too big'

Bug #2119	mysqlbinlog 'Event too big'
Submitted:	15 Dec 2003 12:34	Modified:	26 Apr 2012 19:28
Reporter:	Ken Menken	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S2 (Serious)
Version:	4.0.16	OS:	Linux (Debian Linux)
Assigned to:		CPU Architecture:	Any

Description:
OK, I'm not *positive* this is a 4.0.16 problem as the log was written under 4.0.13, but mysqlbinlog -V returns version 2.4.

Problem is the following:
> mysqlbinlog -r resfile binary-log.181

ERROR: Error in Log_event::read_log_event(): 'Event too big',
data_len=1660944482,event_type=2
ERROR: Could not read entry at offset 9986036 : Error in log format or read
error

Both permanent solutions (e.g. "logs written under 4.0.13 may have this error, so upgrade") and advice on how to extract everything in this particular log file after 9986036 (assuming that line cannot be read) would be appreciated. 

How to repeat:
I wish I knew! I'd have to give you our binlog... by the way, the log is 11 MB, and we've used much larger ones without trouble.

Please upload a gzip of your binary log to this bugs db.

Click on the "Files" tab.

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".

I got this error recently,i can put on my file ,is't a bug ?

but my file 60M ，how can i upload ? tks

Yao,

version 4.0.16 is very old and in modern versions code changed. Please open new report, describe which version you use, by which version binary log has been created and upload it how described in "Files" section.