Quantcast
Channel: MySQL Forums - Replication
Viewing all articles
Browse latest Browse all 1562

confusing slave and master server ids (1 reply)

$
0
0
I'm trying to set up master->slave->slave2 replication using servers DB2, DB210, and DB212 with respective server ids 2, 210, and 212. Replication works fine from DB2 (5.1.60) to DB210 (5.5.27). I did a STOP SLAVE on DB210 and backed up the databases, then restored them to DB212 (5.5.28). At the same time I did SHOW MASTER STATUS on DB210 to get the replication starting point for DB212. I did START SLAVE on DB210 and let it catch up - worked fine. I did CHANGE MASTER on DB212 to set the starting point - worked fine.

When I try to START SLAVE on DB212 I get the error message "Slave I/O: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work (or the --replicate-same-server-id option must be used on slave but this does not always make sense; please check the manual before using it). Error_code: 1593". When I SHOW SLAVE STATUS\G I see "Master_Server_Id: 212", which is the local server id. If I SET GLOBAL server_id = 44 and START SLAVE, I see "Master_Server_Id: 44" and slave I/O has stopped with the same error. Somehow MySQL is seeing the local server_id as the Master_Server_Id. What have I missed?

Viewing all articles
Browse latest Browse all 1562

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>