MySQL複製環境Slave報錯"Got fatal error 1236 from master when reading data"
MySQL複製環境Slave節點報錯
mysql> show slave status\G
*************************** 1. row ***************************
Slave_IO_State:
Master_Host: 10.20.30.10
Master_User: repl
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000008
Read_Master_Log_Pos: 920
Relay_Log_File: mysqld-relay-bin.000018
Relay_Log_Pos: 4
Relay_Master_Log_File: mysql-bin.000008
Slave_IO_Running: No
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: 920
Relay_Log_Space: 154
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_SSL_Verify_Server_Cert: No
Last_IO_Errno: 1236
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1
Master_UUID: 203fe772-177e-11e7-b15c-000c296b3b20
Master_Info_File: /mysql_data_57/master.info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp: 170624 17:03:05
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set:
Executed_Gtid_Set:
Auto_Position: 0
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:
1 row in set (0.00 sec)
在Master節點上檢視二進位制日誌的位置
mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000011 | 1734 | | | |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)
檢視Master節點的二進位制日誌
mysql> show master logs;
+------------------+-----------+
| Log_name | File_size |
+------------------+-----------+
| mysql-bin.000010 | 3780 |
| mysql-bin.000011 | 1734 |
+------------------+-----------+
2 rows in set (0.06 sec)
檢視Slave節點的二進位制日誌
mysql> show binary logs;
+------------------+-----------+
| Log_name | File_size |
+------------------+-----------+
| mysql-bin.000008 | 154 |
| mysql-bin.000009 | 154 |
+------------------+-----------+
2 rows in set (0.02 sec)
報錯原因:
在Master節點上刪除了二進位制日誌,導致Slave節點的IO執行緒獲取不到指定的二進位制日誌
在Master節點上設定了自動刪除二進位制日誌的引數,5天后會自動刪除二進位制日誌;而Slave節點所在的資料庫一直沒有啟動,再次啟動時IO執行緒獲取不到Master節點的二進位制日誌
mysql> show variables like '%expire%';
+--------------------------------+-------+
| Variable_name | Value |
+--------------------------------+-------+
| disconnect_on_expired_password | ON |
| expire_logs_days | 5 |
+--------------------------------+-------+
2 rows in set (0.02 sec)
解決方法:
除非主庫有二進位制日誌備份,否則需要重建Slave節點
mysql> show slave status\G
*************************** 1. row ***************************
Slave_IO_State:
Master_Host: 10.20.30.10
Master_User: repl
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000008
Read_Master_Log_Pos: 920
Relay_Log_File: mysqld-relay-bin.000018
Relay_Log_Pos: 4
Relay_Master_Log_File: mysql-bin.000008
Slave_IO_Running: No
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: 920
Relay_Log_Space: 154
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_SSL_Verify_Server_Cert: No
Last_IO_Errno: 1236
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1
Master_UUID: 203fe772-177e-11e7-b15c-000c296b3b20
Master_Info_File: /mysql_data_57/master.info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp: 170624 17:03:05
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set:
Executed_Gtid_Set:
Auto_Position: 0
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:
1 row in set (0.00 sec)
mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000011 | 1734 | | | |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)
檢視Master節點的二進位制日誌
mysql> show master logs;
+------------------+-----------+
| Log_name | File_size |
+------------------+-----------+
| mysql-bin.000010 | 3780 |
| mysql-bin.000011 | 1734 |
+------------------+-----------+
2 rows in set (0.06 sec)
mysql> show binary logs;
+------------------+-----------+
| Log_name | File_size |
+------------------+-----------+
| mysql-bin.000008 | 154 |
| mysql-bin.000009 | 154 |
+------------------+-----------+
2 rows in set (0.02 sec)
報錯原因:
在Master節點上刪除了二進位制日誌,導致Slave節點的IO執行緒獲取不到指定的二進位制日誌
在Master節點上設定了自動刪除二進位制日誌的引數,5天后會自動刪除二進位制日誌;而Slave節點所在的資料庫一直沒有啟動,再次啟動時IO執行緒獲取不到Master節點的二進位制日誌
mysql> show variables like '%expire%';
+--------------------------------+-------+
| Variable_name | Value |
+--------------------------------+-------+
| disconnect_on_expired_password | ON |
| expire_logs_days | 5 |
+--------------------------------+-------+
2 rows in set (0.02 sec)
除非主庫有二進位制日誌備份,否則需要重建Slave節點
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26506993/viewspace-2141222/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MySQL主從複製報錯:Got fatal error 1236 from master when reading data fromMySqlGoErrorAST
- MySQL案例09:Last_IO_Error: Got fatal error 1236 from master when reading data from binary logMySqlASTErrorGo
- Last_IO_Error: Got fatal error 1236ASTErrorGo
- 故障案例:主從同步報錯Fatal error: The slave I/O thread stops because master and slave have equal MySQL server主從同步ErrorthreadASTMySqlServer
- MySQL報錯Slave: received end packet from server, apparent master shutdownMySqlServerAPPAST
- Mysql Master-slave複製簡單配置記錄MySqlAST
- Mysqldump實現mysql的master-slave主從複製MySqlAST
- MySQL主從同步報error 1236MySql主從同步Error
- mysql 8 報錯 ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repositoryMySqlErrorAIStruct
- Innobackupex實現mysql線上搭建master-slave主從複製MySqlAST
- 1.MongoDB 2.7主從複製(master –> slave)環境基於時間點的恢復MongoDBAST
- MySQL複製跳過錯誤--slave_skip_errors、sql_slave_skip_counter、slave_exec_modeMySqlError
- MySQL 5.6複製報錯Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND;MySqlError
- MySQL主從複製環境部署MySql
- MySQL 8.0.26 bug ERROR 1064(42000) -master-data is deprecated and will be removeMySqlErrorASTREM
- MySQL複製命令slave被REPLICA命令取代MySql
- 解決ERROR 1030 (HY000): Got error 168 from storage engine apparmorErrorGoAPP
- Windows 環境下,MySQL 的主從複製和主主複製WindowsMySql
- windows環境下,Mysql的主從複製和主主複製WindowsMySql
- The slave I/O thread stops because master and slave have equal MySQL server UUIDthreadASTMySqlServerUI
- Mysql:1236常見錯誤MySql
- MySQL 5.7從庫報錯exceeds of slave_pending_jobs_size_max. Error_code: 1864MySqlError
- 生產環境中MySQL複製的搭建KPMySql
- 半同步複製報錯mysql8.0.25MySql
- Mysql 5.6 Master和Slave 主備切換MySqlAST
- Fatal NI connect error 12170 錯誤Error
- GTID複製報錯處理:Last_Error: Error 'Can't drop database 'test';ASTErrorDatabase
- git push origin master 時出現報錯 error: src refspec master does not match any error: failed to push someGitASTErrorAI
- MySQL主從複製配置引數 -- logs-slave-updatesMySql
- fatal: [192.168.65.128]: UNREACHABLE! => {"changed": false, "msg": "SSH Error: data could not be senFalseError
- mysqldump匯出報錯"mysqldump: Error 2013 ... during query when dumping tableMySqlError
- windows終端輸入pip install requests報錯:Fatal error in launcherWindowsError
- Pytorch複製現有環境PyTorch
- MySQL 複製全解析 Part 1 實驗環境介紹MySql
- MySQL5.7半同步複製報錯案例分析MySql
- MySQL 網路導致的複製報錯案例MySql
- Docker安裝MySQL8.0.39報錯:Fatal glibc error: CPU does not support x86-64-v2DockerMySqlError
- mysqldump Got error: 1045MySqlGoError
- mysqldump Got error 1290MySqlGoError