MySQL Delete mysql-bin.000xxx file causes MySQL to not start workaround

When you start MySQL prompts MySQL to start, view the system event log as follows

Could not open log file

Can't read the log file can not open, at the time to the MySQL data directory of a xxxx-b59093774c.err error file, open the following a section of code

The

141019 22:35:49 [note] Plugin ' federated ' is disabled.
141019 22:35:49 innodb:the InnoDB memory heap are disabled
141019 22:35:49 innodb:mutexes and Rw_locks use Windo WS interlocked functions
141019 22:35:49 innodb:compressed tables use zlib 1.2.3
141019 22:35:49 Innodb:initiali Zing buffer pool, size = 128.0M
141019 22:35:49 innodb:completed initialization of buffer pool
141019 22:35:49 in Nodb:highest supported the file format is barracuda.
141019 22:35:50  innodb:waiting for the background threads to start
141019 22:35:51; Log sequence number 22869842
X:/vsr/mpyx/bin/mysqld:file './mysql-bin.000574 ' not Found (errcode:2)
141019 22:3 5:51 [ERROR] Failed to open log (file './mysql-bin.000574 ', errno 2)
141019 22:35:51 [ERROR] could not open log file 141019 22:35:51 [ERROR] Can ' t init TC log
141019 22:35:51 [ERROR] aborting

141019 22:35:51 innodb:starting shutdown ...
141019 22:35:51 Innodb:shutdown completed; Log sequence Number 22869842
141019 22:35:51 [note] X:/vsr/mpyx/bin/mysqld:shutdown complete

Watch my hair, there's one of them.

X:/vsr/mpyx/bin/mysqld:file './mysql-bin.000574 ' not Found (errcode:2)
141019 22:35:51 [ERROR] Failed to open log (file './mysql-bin.000574 ', errno 2)

Code, meaning that the batch/mysql-bin.000574 file does not exist, now resolved, I just deleted the file in the recovery station directly restore/mysql-bin.000574 file restart found MySQL started normal oh

Summary, MySQL if there are a large number of binary log files we must note that the retention ID for the largest one do not delete or directly in My.inik to turn off MySQL binary log generation to resolve this issue.