EasyPHP 解决 Unexpected end of mysql 的方法


今天在启动easyphp的时候,发生了 Unexpected end of mysql 错误,无法启动mysql。但是很快就找到了解决Unexpected end of mysql发放。


1.产生Unexpected end of mysql问题原因回顾:没有退去easyphp,直接关闭计算机。

2.重启计算机,重启easyphp,提示 Unexpected end of mysql ,无法启动mysql。


2013-08-01 11:00:30 5164 [Note] Plugin ‘FEDERATED’ is disabled.
2013-08-01 11:00:30 1754 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB’s internal memory allocator.
2013-08-01 11:00:30 5164 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-01 11:00:30 5164 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-01 11:00:30 5164 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-01 11:00:30 5164 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-01 11:00:30 5164 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-01 11:00:30 5164 [Note] InnoDB: Completed initialization of buffer pool
2013-08-01 11:00:30 5164 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-01 11:00:30 5164 [Note] InnoDB: The log sequence numbers 3410038 and 3410038 in ibdata files do not match the log sequence number 3415096 in the ib_logfiles!
2013-08-01 11:00:30 5164 [Note] InnoDB: Database was not shutdown normally!
2013-08-01 11:00:30 5164 [Note] InnoDB: Starting crash recovery.
2013-08-01 11:00:30 5164 [Note] InnoDB: Reading tablespace information from the .ibd files…
2013-08-01 11:00:30 5164 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .mysqlslave_relay_log_info.ibd. Cannot open tablespace wpwpwp/wp_terms which uses space ID: 3 at filepath: .wpwpwpwp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .wpwpwpwp_terms.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.


在 my.ini 文件添加如下代码:

innodb_force_recovery = 1


人吐槽 人点赞



用户名: 密码:
验证码: 匿名发表


查看评论:EasyPHP 解决 Unexpected end of mysql 的方法