Bug #86685 Binolog corruption when using MEB 3.12.1 on mysql server on windows 2012 r2

• Submitted: 13 Jun 2017 18:51
• Modified: 13 Jul 2017 0:51
• Reporter: Sadat Iddrisu
• Status: Verified
• Category: MySQL Server: Replication
• Severity: S1 (Critical)
• Version: 5.6.25
• OS: Windows
• CPU Architecture: Any
• Tags: Mysql Binlog crash safe

[13 Jun 2017 18:51] Sadat Iddrisu

Description:
2017-05-23 23:02:32 2872 [ERROR] MYSQL_BIN_LOG::move_crash_safe_index_file_to_index_file failed to move crash_safe_index_file to index file.
2017-05-23 23:02:32 2872 [ERROR] MYSQL_BIN_LOG::add_log_to_index failed to move crash safe index file to index file.
2017-05-23 23:02:32 2872 [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.
2017-05-23 23:02:32 2872 [ERROR] Could not open .\mysql-bin.000192 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.
2017-05-23 23:02:32 2872 [ERROR] The server was unable to create a new log file. An incident event has been written to the binary log which will stop the slaves.

Error above is is what we see in 2 of our error logs, and replication is stopped as a result. 

We removed corrupted logs and restarted the instance, new binary logs were created, and lasted a week until binary logs corrupted again.

In the meantime, we've discontinued using MEB 3.12.1 on these servers. 

Wanted to know if any, what the long term solution is for this?

How to repeat:
automate backup creation via MEB, and after a while binlog crashes, disabled, by server, and disabling binary logging

[6 Jul 2017 21:32] Sadat Iddrisu

Any status on this issue?

Thanks

Sadat Iddrisu

[13 Jul 2017 0:51] MySQL Verification Team

Hi,

thanks for the report, I verified the bug as described.

--skip-binlog and --skip-relaylog would work as a workaround

bug is partially already fixed in 5.6.32 and 5.7.14.

best regards
Bogdan

[21 Sep 2017 16:15] Telemisis Support

This is an issue in MySQL 5.7.15