>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
quot; <[EMAIL PROTECTED]>
>>Aan: mysql@lists.mysql.com
>>CC: "Gleb Paharenko" <[EMAIL PROTECTED]>
>>Onderwerp : Re: Error reading binlog - recoverable?
>>
>>Hi Gleb,
>>
>>Thank you for you reply.
>>
>>I am very much willing to r
error
Is there anything else I can try?
Martijn
> Datum: 08/02/06 01:52 PM
> Van: "Martijn van den Burg" <[EMAIL PROTECTED]>
> Aan: mysql@lists.mysql.com
> CC: "Gleb Paharenko" <[EMAIL PROTECTED]>
> Onderwerp : Re: Error reading binlog - recoverab
MAIL PROTECTED]>
> Aan: mysql@lists.mysql.com
> CC:
> Onderwerp : Re: Error reading binlog - recoverable?
>
> Hello.
>
> If the data in binary logs is important for you and you're ready to
> research and recover the data manually. Have a look here:
>http://dev.m
Hello.
If the data in binary logs is important for you and you're ready to
research and recover the data manually. Have a look here:
http://dev.mysql.com/doc/internals/en/replication-binary-log.html
Check if the problem still exists with mysqlbinlog from the fresh MySQL
shipment. The --hexdump
Hi,
MySQL 4.1.10-log, Solaris
Replication stopped with an error that closely resembles bug #8215. When
examining the binlog with mysqlbinlog, it stops before reaching the end of the
binlog, with the error
ERROR: Error in Log_event::read_log_event(): 'Event too big', data_len:
1635131433, eve
