电脑断电后启动电脑,启动mantis时发现mysql服务无法启动
2018-01-17 16:14
316 查看
打开mysql日志发下如下错误日志:
2018-01-17 15:55:50 4988 [Note] Plugin 'FEDERATED' is disabled.
2018-01-17 15:55:50 4988 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-17 15:55:50 4988 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-01-17 15:55:50 4988 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-01-17 15:55:50 4988 [Note] InnoDB: Not using CPU crc32 instructions
2018-01-17 15:55:50 4988 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-01-17 15:55:50 4988 [Note] InnoDB: Completed initialization of buffer pool
2018-01-17 15:55:50 4988 [Note] InnoDB: Highest supported file format is Barracuda.
2018-01-17 15:55:50 4988 [Note] InnoDB: The log sequence numbers 1603124 and 1603124 in ibdata files do not match the log sequence number 1603134 in the ib_logfiles!
2018-01-17 15:55:50 4988 [Note] InnoDB: Database was not shutdown normally!
2018-01-17 15:55:50 4988 [Note] InnoDB: Starting crash recovery.
2018-01-17 15:55:50 4988 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-01-17 15:55:50 4988 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace hmail/cache uses space ID: 42 at filepath: .\hmail\cache.ibd. Cannot open tablespace mail/cache which uses space ID: 42 at filepath: .\mail\cache.ibd
2018-01-17 15:55:50 1480 InnoDB: Operating system error number 997 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html InnoDB: Error: could not open single-table tablespace file .\mail\cache.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
-------------
到wamp的mysql的安装目录:D:\wamp\bin\mysql\mysql5.6.12\data
将文件夹下的两个文件ib_logfile0 和 ib_logfile1 改名或者删除,再次启动mysql服务,服务正常启动。系统会自动再重新生成这两个文件。
2018-01-17 15:55:50 4988 [Note] Plugin 'FEDERATED' is disabled.
2018-01-17 15:55:50 4988 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-17 15:55:50 4988 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-01-17 15:55:50 4988 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-01-17 15:55:50 4988 [Note] InnoDB: Not using CPU crc32 instructions
2018-01-17 15:55:50 4988 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-01-17 15:55:50 4988 [Note] InnoDB: Completed initialization of buffer pool
2018-01-17 15:55:50 4988 [Note] InnoDB: Highest supported file format is Barracuda.
2018-01-17 15:55:50 4988 [Note] InnoDB: The log sequence numbers 1603124 and 1603124 in ibdata files do not match the log sequence number 1603134 in the ib_logfiles!
2018-01-17 15:55:50 4988 [Note] InnoDB: Database was not shutdown normally!
2018-01-17 15:55:50 4988 [Note] InnoDB: Starting crash recovery.
2018-01-17 15:55:50 4988 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-01-17 15:55:50 4988 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace hmail/cache uses space ID: 42 at filepath: .\hmail\cache.ibd. Cannot open tablespace mail/cache which uses space ID: 42 at filepath: .\mail\cache.ibd
2018-01-17 15:55:50 1480 InnoDB: Operating system error number 997 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html InnoDB: Error: could not open single-table tablespace file .\mail\cache.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
-------------
到wamp的mysql的安装目录:D:\wamp\bin\mysql\mysql5.6.12\data
将文件夹下的两个文件ib_logfile0 和 ib_logfile1 改名或者删除,再次启动mysql服务,服务正常启动。系统会自动再重新生成这两个文件。
相关文章推荐
- 电脑非正常关机后导致wamp的mysql服务无法启动
- MySQL 服务无法启动
- mysql 服务无法启动
- MySQL无法启动 服务没有报告任何错误
- mysql的服务已经停止,无法启动的解决办法
- Windows下无法启动MYSQL服务”1067 进程意外终止”解决办法
- windows无法启动mysql服务,错误提示1067
- 无法启动MYSQL服务”1067 进程意外终止”解决的方法——从源头分析(从根本解决)
- MySQL服务无法启动 无任何错误报告 键入net helpmsg 3534
- MySQl的意外断电后无法启动
- MySql服务无法启动系统出错发生系统错误1067进程意外终止,另类原因
- [置顶] mysql服务无法启动 服务没有报告任何错误解决方法
- MySQL 服务无法启动 ERROR 2003 (HY000): Can't connect to MySQL server on 'localhost' (10061)
- MySql安装之后无法启动服务(如在管理中打开显示进程意外终止)
- 无法启动xampp中的mysql服务,端口又未被占用
- 解决Windows安装解压版MySQL出现服务正在启动-服务无法启动的问题
- MySQL免安装教程 - 服务无法启动可恶的 1067 错误
- 今天以zip模式在windows10 64位环境下安装mysql5.7,到最后一步提示mysql服务无法启动。
- 解决MYSQL免安装版服务无法启动问题
- VMware Vcenter 由于断电重启之后,服务无法启动