Hi all-- We have one master and 12 slaves replicating from it. Server is 4.0.16 (havn't wanted to take it down to upgrade), the slaves are 4.0.17, all running on RedHat AS. Lately, every few hours one of the machines caughs up this error, and quits replicating:
Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. It's complaining about a corrupted relay-log, but it's always only one machine at a time. When I run 'mysqlbinlog <offending relay-log-file>' it gives me the following error: ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 396, event_type: 2 ERROR: Could not read entry at offset 60096864 : Error in log format or read error The offending log in the current case is _not_ the last one, so the IO thread is appearently still functional. The only fix I know is to blow away the data on the slaves and start again with a fresh snapshot (including master.info). As far as I know there's no disk problems (all servers less than a year old, and lots of space available). Any thoughts? -Matt- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
