Here is the scenario:
4.0.15 as the master
3.23.57 is the slave
I can't get them to replicate until I downgraded 4.0.15 to 3.23.57
This was the error produced
030911 23:45:47 Slave: connected to master '[EMAIL PROTECTED]:3306',
replication star
ted in log 'FIRST' at position 79
030911 23:45:47 Slave: did not get the expected error running query
from master - ex
pected: 'Invalid error code' (256), got 'no error' (0)
030911 23:45:47 Slave: error running query ''
030911 23:45:47 Error running query, slave aborted. Fix the problem,
and re-start th
e slave thread with "mysqladmin start-slave". We stopped at log 'FIRST'
position 79
030911 23:45:47 Slave thread exiting, replication stopped in log
'FIRST' at position 79
I was under the impression that replication between 3.23.x and 4.0.x is
possible.
I did check and make sure that
CHANGE MASTER TO MASTER_LOG_FILE='another_log_file', MASTER_LOG_POS=4;
was executed.
On 4.0.15 I made sure the REPLICATION user had REPLICATION permissions.
A Connection was made did change the log position from 4 to 79, then
replication could not continue even with SET
SQL_SLAVE_SKIP_COUNTER=x;slave start;
I did a Google search on the error message, and saw no solutions to this
problem.
Any suggestions?
- Dathan Vance Pattishall
- Sr. Programmer and mySQL DBA for FriendFinder Inc.
- http://friendfinder.com/go/p40688
