Problems with Replication

[sostek]

We're replicating several databases from a master running 4.1.10 to one slave running 4.1.10 and another running 5.0.3

I get the following error when I show slave status on the slave:

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.

I've run the mysqlbinlog on both the master and slave but am unsure of what to do with it.

I've tried the SET GLOBAL SQL_SLAVE_SKIP_COUNTER to 1 and 2 and then stop/start the slave and my SQL slave thread still wont' run.

Any help would be appreciated.

Tony

 

[sostek]

Disregard. We ended up finding the offending record in the relay log and just using the

change master to {field name, like relay_log_pos} = value

Then stop the slave and start again.

Probably a good idea to perform a load data from master on the slave at some point just to be sure everything is in a known state.