我们收到以下错误。
2016-03-08 15:32:09 1184 [ERROR] MYSQL_BIN_LOG::move_crash_safe_index_file_to_index_file failed to move crash_safe_index_file to index file.
2016-03-08 15:32:09 1184 [ERROR] MYSQL_BIN_LOG::add_log_to_index failed to move crash safe index file to index file.
2016-03-08 15:32:09 1184 [ERROR] Could not use (null) for logging (error 9). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
2016-03-08 15:32:09 1184 [ERROR] Could not open E:\Program Files\MySQL\MySQL Server 5.6\data\bin_relay_logs\relay\mysql-relay-log.001641 for logging (error 9). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
2016-03-08 15:32:09 1184 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Error_code: 1595
2016-03-08 15:32:09 1184 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Error_code: 1595
2016-03-08 15:32:09 1184 [ERROR] Error reading relay log event: error switching to the next log
2016-03-08 15:32:09 1184 [Note] Slave I/O thread exiting, read up to log 'mysql-bin-log.000821', position 4
2016-03-08 15:32:09 1184 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 1594
2016-03-08 15:32:09 1184 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin-log.000820' position 104878880我搜索了很多帖子,但都找不到解决办法。有人找到解决办法了吗?
最重要的是,为什么会发生这种情况?
MySQL版本: 5.6.24在windows平台上
Windows服务器是虚拟服务器。
当系统在主主复制中运行时发生这种情况,并为DR. .
发布于 2016-03-21 07:55:33
将此问题提交给Oracle支持。
这个问题是甲骨文开发团队仍在努力解决的问题。
问题: MySQL企业备份尝试备份所有的绑定日志,在此期间,内部机制无法备份绑定日志并使DB崩溃。甲骨文的开发仍在努力解决这个问题。
解决办法:避免在增量备份和完全备份中对二进制日志和中继日志进行备份。
https://dba.stackexchange.com/questions/131696
复制相似问题