Mysql服务启动失败 [Server] I/O error reading the header from the binary log.

错误信息如下:

2020-12-08T08:41:34.003470Z 0 [ERROR] [MY-010958] [Server] I/O error reading the header from the binary log.
2020-12-08T08:41:34.004821Z 0 [ERROR] [MY-010041] [Server] Can't init tc log
2020-12-08T08:41:34.006049Z 0 [ERROR] [MY-010119] [Server] Aborting

-----------

2020-12-08T08:49:00.150380Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.19) starting as process 13436
mysqld: File '.\DESKTOP-IR5UPKH-bin.000033' not found (OS errno 2 - No such file or directory)
2020-12-08T08:49:02.906655Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2020-12-08T08:49:02.907263Z 0 [ERROR] [MY-010041] [Server] Can't init tc log
2020-12-08T08:49:02.907913Z 0 [ERROR] [MY-010119] [Server] Aborting

 

故障排除步骤:

1. Mysql服务启动失败,到Mysql安装目录下查找错误日志(DESKTOP-IR5UPKH.err是"计算机名".err):

    C:\ProgramData\MySQL\MySQL Server 8.0\Data\DESKTOP-IR5UPKH.err

2. 错误信息如下:

2020-12-08T08:41:34.003470Z 0 [ERROR] [MY-010958] [Server] I/O error reading the header from the binary log.
2020-12-08T08:41:34.004821Z 0 [ERROR] [MY-010041] [Server] Can't init tc log
2020-12-08T08:41:34.006049Z 0 [ERROR] [MY-010119] [Server] Aborting

3.根本原因:

  Mysql的日志文件出错,很可能是你自己创建了一个与之前日志名相同的文件,但是Mysql知道文件已经不是原有的日志文件了。我的错误就是删除原有的日志文件,然后自己创建了一个同名的日志文件导致的。

4.解决方案:

  a.定位到当前日志文件位置,我的是:C:\ProgramData\MySQL\MySQL Server 8.0\Data\DESKTOP-IR5UPKH-bin.000033

  b. 删除错误的日志文件:DESKTOP-IR5UPKH-bin.000033

  c.打开同级目录下的日志索引文件:C:\ProgramData\MySQL\MySQL Server 8.0\Data\DESKTOP-IR5UPKH-bin.index,并删除刚刚删除日志文件的那一行

    

  d.保存并重启Mysql服务,问题解决。

  e.如果没有解决,继续查看错误日志(DESKTOP-IR5UPKH.err)里面的详细内容解决,一般是再删除index文件里没有的日志文件行,重启服务即可。

  

 

posted on 2020-12-08 17:11  两轮明月  阅读(1891)  评论(0编辑  收藏  举报

导航