MySQL主从同步报错,server-id一致导致报错
Posted
tags:
篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了MySQL主从同步报错,server-id一致导致报错相关的知识,希望对你有一定的参考价值。
今天新加入一台从库,进行同步master数据,但是my.cnf配置文件直接拷贝,没修改server-id,导致报错:
2017-04-01 14:57:16 140661325472512 [Note] Slave: received end packet from server, apparent master shutdown: 2017-04-01 14:57:16 140661325472512 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘mysql-bin.000037‘ at position 355680160 2017-04-01 14:57:16 140661325472512 [Note] Slave: received end packet from server, apparent master shutdown: 2017-04-01 14:57:16 140661325472512 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘mysql-bin.000037‘ at position 355687180 2017-04-01 14:57:17 140661325472512 [Note] Slave: received end packet from server, apparent master shutdown: 2017-04-01 14:57:17 140661325472512 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘mysql-bin.000037‘ at position 355701274 2017-04-01 14:57:18 140661325472512 [Note] Slave: received end packet from server, apparent master shutdown: 2017-04-01 14:57:18 140661325472512 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘mysql-bin.000037‘ at position 355723904 2017-04-01 14:57:18 140661325472512 [Note] Slave: received end packet from server, apparent master shutdown: 2017-04-01 14:57:18 140661325472512 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘mysql-bin.000037‘ at position 355734536 2017-04-01 14:57:19 140661325472512 [Note] Slave: received end packet from server, apparent master shutdown: 2017-04-01 14:57:19 140661325472512 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘mysql-bin.000037‘ at position 355736849 2017-04-01 14:57:19 140661325472512 [Note] Slave: received end packet from server, apparent master shutdown: 2017-04-01 14:57:19 140661325472512 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘mysql-bin.000037‘ at position 355740978 2017-04-01 14:57:20 140661325472512 [Note] Slave: received end packet from server, apparent master shutdown: 2017-04-01 14:57:20 140661325472512 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log ‘mysql-bin.000037‘ at position 355740978
查看主从同步状态
>show slave status\G; Relay_Master_Log_File: mysql-bin.000037 Slave_IO_Running: Preparing Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 354949769 Relay_Log_Space: 30906 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: NULL
遇到该报错信息:
查找master和slave主从上的server-id设置是否相同
查找slave1和slave2从和从之间的server-id设置是否相同了,也会导致该问题
每台master和slave主从库的server-id都必须唯一,识别主从的库的唯一标识
以上是关于MySQL主从同步报错,server-id一致导致报错的主要内容,如果未能解决你的问题,请参考以下文章
主从复制报错Fatal error:The slave I/O thread stops because master and slave have equal MySQL server UUIDs;