I highly recommend you update the slave to the same version as the master.
Mark D. Wallace wrote:
> I'm trying to set up a replication database and cannot get the slave
> to parse the log files on the master.
> The slave is connecting to the master as indicated in the log file.
>
> I have tried to connect directly to the master database from the mysql
> client on the slave and have no problem using the replication username
> and password.
>
> The master server is mysql-3.23.37-pc-linux-gnu-i686
> The slave server is mysql mysql-3.23.51-pc-linux-gnu-i686
> From the Mysql site, these two are compatible as a slave master pair.
>
> The error message from the slaves error log reads.
>
>
> 14:28:38 Slave: connected to master 'repl@stripped:3306',
> replication started in
> log 'FIRST' at position 4
>
> 020813 14:28:38 Could not parse log event entry, check the master for
> binlog corruption
> This may also be a network problem, or just a bug in
> the master or slave code.
>
> (WHAT IS THE NAME OF THE LOG FILE THE SLAVE IS TRYING TO READ????
> mysql.log?)
>
> 020813 14:28:38 Error running query, slave aborted. Fix the problem,
> and re-start the slave thread with
> "mysqladmin start-slave". We stopped at log 'FIRST' position 4
>
> 020813 14:28:38 Slave thread exiting, replication
> stopped in log 'FIRST' at position 4
>
>
> WHAT is "log 'FIRST' at position 4" referencing?
>
>
> Thanks for any help you can provide.
>
> Mark Wallace
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail <mysql-thread117016@stripped>
> To unsubscribe, e-mail
> <mysql-unsubscribe-gerald_clark=suppliersystems.com@stripped>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>
