Description:
Replication may start logging the following error message on the slave with little clue about what is happening.
080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444286437
080603 20:53:10 [Note] Slave: received end packet from server, apparent master shutdown:
080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'master-bin.003676' position 444292333
080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444292333
080603 20:53:10 [Note] Slave: received end packet from server, apparent master shutdown:
080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'master-bin.003676' position 444294573
080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444294573
080603 20:53:10 [Note] Slave: received end packet from server, apparent master shutdown:
080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'master-bin.003676' position 444298239
080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444298239
How to repeat:
Set two slave to have same server-id and start replication..
Suggested fix:
Add more descriptive error message.