【MySQL】MySQL同步报错-> received end packet from server, apparent master shutdown: Slave I/O thread: Failed reading log event, reconnecting to retry报错解决和分析

[root@db-ft-db-48 ~]# tail -f /mysqlLog/beside_index_err.log
140102 20:42:26 [Note] Slave: received end packet from server, apparent master shutdown:
140102 20:42:26 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.000418' at position 99825711
140102 20:42:26 [Note] Slave: received end packet from server, apparent master shutdown:
140102 20:42:26 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.000418' at position 99827236
140102 20:42:26 [Note] Slave: received end packet from server, apparent master shutdown:
140102 20:42:26 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.000418' at position 99827999
140102 20:42:26 [Note] Slave: received end packet from server, apparent master shutdown:
140102 20:42:26 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.000418' at position 99829772
140102 20:42:26 [Note] Slave: received end packet from server, apparent master shutdown:
140102 20:42:26 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.000418' at position 99832314

今天一组数据库突然报同步延迟很大，发现errlog大量报错，上网查询很多人说是因为server-id主从配置相同导致，进行排查没有发现Master和Slave的server-id相同，又分析半天未果。

因为我们是M-SS架构，所以去了另外一台Slave上去看，发现也有很多同样errlog，也顺便看了下server-id，发现和另外一台Slave的server-id，手动slave stop一台后，另外一台errlog消除，找到问题原因，shutdown后重做配置重启后问题解决。

后续分析下原因。未完待续。