Slave: received 0 length packet from server, apparent master shutdown
又是server-id這個引數的原因
[@more@]過完節第一天檢查資料庫,發現一臺mysql的slave報出大量的
Slave: received 0 length packet from server, apparent master shutdown.
日誌檔案已經2g了.....但是資料倒是還在走,嘗試stop slave再start slave，報錯 ：
Error reading packet from server: log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master (server_errno=1236)
再檢查下mt.cnf果然還是server-id和別的slave的重複造成的，重新設定下第一個錯誤就ok了，第二個錯誤麼可能就是使用了LOAD DATA或者mysqlimp造成的，避免的方法就是在主從2臺上先把要load的文字load到不復制的臨時庫中，再透過sql的方式插入複製的表中，這樣只傳遞sql而不會發生大量資料的傳遞，就不用更改max_allowed_packet 了，否則按照mysql的提示修改雖然能過去，但是下次資料再多點可又要改了，而且還要停master。。。這在生產環境可不是每次都行的
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/79686/viewspace-1016553/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- MySQL報錯Slave: received end packet from server, apparent master shutdownMySqlServerAPPAST
- linux log中大量 Received SNMP packet(s) from UDPLinuxUDP
- 消除linux log中的大量Received SNMP packet(s) from UDPLinuxUDP
- MySQL Master/Slave Master/MasterMySqlAST
- MySQL master and slave have equal MySQL server UUIDsMySqlASTServerUI
- Linux Log中大量snmpd[10932]: Received SNMP packet(s) from UDP[final]LinuxUDP
- Redis master and slaveRedisAST
- MySQL master/slaveMySqlAST
- The slave I/O thread stops because master and slave have equal MySQL server UUIDthreadASTMySqlServerUI
- MySql的Master/SlaveMySqlAST
- master and slave have equal MySQL server UUIDs問題解決ASTMySqlServerUI
- 【Mysql】Slave_IO_Running: No---Got fatal error 1236 from masterMySqlGoErrorAST
- mysql master和slave配置MySqlAST
- mysql slave 轉為 masterMySqlAST
- MySQL 5.5 Master/Slave 配置MySqlAST
- Unknown initial character set index ‘255‘ received from server. Initial client character set can beIndexServerclient
- mysql master slave 主從同步MySqlAST主從同步
- mysql 同步 master-slave薦MySqlAST
- Mysql Slave群切換MasterMySqlAST
- Mysql Slave群切換Master （=）MySqlAST
- Mongodb的master-slave模式與master-master模式實驗MongoDBAST模式
- Server shutdown in progressServer
- Jenkins : 安裝 master 和 slaveJenkinsAST
- 用mysqldump --master-data 建立slaveMySqlAST
- 故障案例：主從同步報錯Fatal error: The slave I/O thread stops because master and slave have equal MySQL server主從同步ErrorthreadASTMySqlServer
- slave之Seconds_Behind_Master析AST
- mysql建立master/slave詳細步驟MySqlAST
- 利用mysql slave 修復master MyISAM tableMySqlAST
- “The last packet sent successfully to the server was 0 milliseconds ago. ”異常解決方案ASTServerGo
- MySQL複製環境Slave報錯"Got fatal error 1236 from master when reading data"MySqlGoErrorAST
- Setup MariaDB Master/Slave Replication for Docker MariaDBASTDocker
- Mysql 5.6 Master和Slave 主備切換MySqlAST
- MySQL錯誤之mysql.slave_master_infoMySqlAST
- MYSQL的master/slave資料同步配置(轉)MySqlAST
- AIX: 'GGS ERROR 190 ... : Received Signal: OMVS Shutdown (33).' [ID 969596.1]AIError
- MYSQL The Server Shutdown Process(筆記)MySqlServer筆記
- mysqld: Sort aborted: Server shutdown in progressMySqlServer
- ORA-16198: LGWR received timedout error from KSRError