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 -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
