【MySQL】MySQL同步报错-> received end packet from server, apparent master shutdown: Slave I/O thread: Failed reading log event, reconnecting to retry报错解决和分析
2014-01-02 20:55
609 查看
[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后重做配置重启后问题解决。
后续分析下原因。未完待续。
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后重做配置重启后问题解决。
后续分析下原因。未完待续。
相关文章推荐
- Slave: received end packet from server, apparent master shutdown
- Slave: received end packet from server, apparent master shutdown:
- Slave: received end packet from server, apparent master shutdown
- Failed reading log event, reconnecting to retry
- 【MySQL】MySQL同步报错-> Last_IO_Error: Got fatal error 1236 from master when reading data from binary log
- Got fatal error 1236 from master when reading data from binary log: 'A slave with the same server_uu
- Lost connection to MySQL server at 'reading authorization packet' 处理解决办法
- Mysql master slave Failed to open the relay log
- mysql报错1872: Slave failed to initialize relay log info structure from the repository
- mysql5.7启动slave报错 ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository
- MS SQL错误:SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems
- MySQL复制错误 The slave I/O thread stopsbecause master and slave have equal MySQL server UUIDs; these UUIDs must bedifferent for replication to work 解析
- MySQL远程连接丢失问题解决方法Lost connection to MySQL server at ‘reading initial communication packet’, system error: 0
- MySql从库的“Reading event from the relay log”问题解决
- ERROR 2013 (HY000): Lost connection to MySQL server at ‘reading authorization packet’, system error: 104原因和解决办法
- Lost connection to MySQL server at 'reading initial communication packet' 错误解决
- 手把手解决Mysql错误:Lost connection to MySQL server at 'reading authorization packet', system error: 0
- Lost connection to MySQL server at 'reading initial communication packet' 错误解决
- 解决lost connection to mysql server at reading initial communication packet
- MySQL复制报错(Slave failed to initialize relay log info structure from the repository)