MySQL Bugs: #81423: When enabling second slave server the firs one stops replication

Bug #81423	When enabling second slave server the firs one stops replication
Submitted:	14 May 2016 3:10	Modified:	5 Jul 2016 0:05
Reporter:	Oscar Salinas	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S2 (Serious)
Version:	5.7.9, 5.7.12	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
I have a master server running on windows server 12 and 2 slave servers running Oracle Linux 7. The problem is that after upgrading the windows server from MySQL 5.7.9 to 5.7.12 one of my slaves servers stop replicating so what I did was to :

STOP SLAVE;
CHANGE MASTER TO MASTER_HOST='ip.master', MASTER_USER='slave_user', MASTER_PASSWORD='some_password', MASTER_LOG_FILE='mysql-bin.006', MASTER_LOG_POS=183;
START SLAVE;

Then I ran 

SHOW SLAVE STATUS;

and the replication started, BUT the problem was that the other slave server stopped replicating, so I did the same for the other server

STOP SLAVE... etc

but exactly at the time I run the query the other server stop running, so it doesn't matter what server I make run the other one stops replication with the Slave_IO_Running NO

Any Idea on how to fix this problem so I can have both slave servers running?
When I had 5.7.9 on all servers I never had the problem 

How to repeat:
One Master server on 5.7.12
Two Slave servers with 5.7.9

try making the 2 slaves work

Hello Oscar Salinas,

Thank you for the report.
Could you please provide the conf files used in the environment(master/slaves) to reproduce the issue at our end? You may want to mark it as private if you prefer after uploading to this bug report.

Thanks,
Umesh

Thank you for providing requested details.
Imho, you are using same server_id for both the slaves i.e "server-id=9" and this is causing the issue. You have to use unique server_id in the replication environment, here “Unique”, means that each ID must be different from every other ID in use by any other replication master or slave.

Similar issue reported Bug #72581

Marking this as not a bug!

Thanks,
Umesh

Im sorry about that, I took the files from the developers pc and is only one main file I just change the server-id and DBs names, but the actual servers have their own server-id number and when I send it to you I only changed the DBs names, but the real servers id are
server-id=9
server-id=11
As I said before upgrading on the main server to 5.7.12, everthing was working fine

Please read my last report about this bug !

I'm still not seeing this issue at my end, could you please provide unaltered error log from problem-ed instances? You may want to mark it as private after uploading here.

Thanks,
Umesh

Please see Bug #72578, I suspect that  copied auto.cnf is causing the issue as I see you are getting "A slave with the same server_uuid as this slave has connected to the master; the first event.." error. Is this the case? Please check

Thanks,
Umesh

Yes it did fix the problem, Thank you, but how come it was working before the upgrade?