MySQL Forums
Forum List  »  Replication

one slave claims binlog corrupt, other is fine
Posted by: Zebee Johnstone
Date: January 16, 2005 07:47PM

I have 3 machines, master and slaveA running 4.0.12 and slaveB running 4.1.8a

(the others will be 4.1.8a Real Soon Now)

SlaveA often stops replicating, with the slave SQL stopped, and nothig in the error log. restarting the slave does nothing, so I restart the server and the error log says
050117 1:18:46 Error in Log_event::read_log_event(): 'Event too big', data_len
050117 1:18:46 Error reading relay log event: slave SQL thread aborted because
of I/O error
050117 1:18:46 Could not parse log event entry, check the master for binlog co
This may also be a network problem, or just a bug in the master or slave code
050117 1:18:46 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'travelmall.377' position 62108
050117 1:18:46 Slave I/O thread: connected to master '', replication started in log 'travelmall.377' at position 112556
050117 01:18:53 mysqld ended

However, slaveB is happily replicating away as far as I can see. Both threads running, no errors, Read_Master_Log_Pos and Exec_Master_Log_Pos both equal to the master status.

What could be causing this corruption that seems to upset binlog and SlaveA but not SlaveB? Is there a way to recover that doesn't involve dumping the master and recreating the slave from that dump?


Options: ReplyQuote

Written By
one slave claims binlog corrupt, other is fine
January 16, 2005 07:47PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.