>I tried mysqlbinlog for 5.0.18, but whether I use the --hexdump option
>or not, it still aborts with the same error:
>
>ERROR: Error in Log_event::read_log_event(): 'Event too big', data_len:
>1635131433, event_type: 109
>Could not read entry at offset 1384:Error in log format or read error
This looks like it's past the end of the binlog file, or very near
the end. Check to see if the file is larger than the location the
slave is looking at.
>Is there anything else I can try?
I'd consider doing the mysqlbinlog on the binlog file piped '|' into
tail to see what the last log entry looks like. I've seen this kind
of an error when the machine crashes and the whole binlog entry doesn't
make it into the file.
If this is the case you can either skip to the next binlog or try
skipping the log entry via
SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1;START SLAVE;
Brad Eacker ([EMAIL PROTECTED] ne [EMAIL PROTECTED])
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
