Hi Gleb, Thank you for you reply.
I am very much willing to recover the data manually, since I am reluctant to bring down our production environment. I checked out the binlog-link you mentioned, but since mysqlbinlog quits with an error, it is of little use. I am now compiling 5.0.18 to see if the --hexdump option will work on the corrupt binlog file. If it does, I presume I can just do a 'mysqlbinlog binlog.xxx | egrep -v ^#' and feed the results back into MySQL, right? Best regards, Martijn > Datum: 08/02/06 01:12 PM > Van: "Gleb Paharenko" <[EMAIL 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.mysql.com/doc/internals/en/replication-binary-log.html > > Check if the problem still exists with mysqlbinlog from the fresh MySQL > shipment. The --hexdump option for mysqlbinlog can be helpful for > debugging purposes. See: > http://dev.mysql.com/doc/refman/5.0/en/mysqlbinlog.html > > > > Martijn van den Burg wrote: > > 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, event_type: 109 > > Could not read entry at offset 1384:Error in log format or read error > > > > Is there a way to recover the remainder of the binlog, and thus restart > > replication without the need to start from scratch? > > > > Regards, > > > > Martijn > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
