XAMPP无法启动MySql

最新推荐文章于 2024-03-12 16:11:20 发布

stoneson

最新推荐文章于 2024-03-12 16:11:20 发布

阅读量1.6k

点赞数

分类专栏： mysql

mysql 专栏收录该内容

3 篇文章 0 订阅

订阅专栏

用XAMPP启动Apache可以，但是启动MySQL就不行。

mysql_error的log记录如下:

2013-08-24 23:43:37 8704 [Note] Plugin 'FEDERATED' is disabled.

2013-08-24 23:43:37 2924 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-24 23:43:37 8704 [Note] InnoDB: The InnoDB memory heap is disabled

2013-08-24 23:43:37 8704 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2013-08-24 23:43:37 8704 [Note] InnoDB: Compressed tables use zlib 1.2.3

2013-08-24 23:43:37 8704 [Note] InnoDB: Not using CPU crc32 instructions

2013-08-24 23:43:37 8704 [Note] InnoDB: Initializing buffer pool, size = 16.0M

2013-08-24 23:43:37 8704 [Note] InnoDB: Completed initialization of buffer pool

2013-08-24 23:43:37 8704 [Note] InnoDB: Highest supported file format is Barracuda.

2013-08-24 23:43:37 8704 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2637108 in the ib_logfiles!

2013-08-24 23:43:37 8704 [Note] InnoDB: Database was not shutdown normally!

2013-08-24 23:43:37 8704 [Note] InnoDB: Starting crash recovery.

2013-08-24 23:43:37 8704 [Note] InnoDB: Reading tablespace information from the .ibd files...

2013-08-24 23:43:37 8704 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace blog_demo/wp_usermeta uses space ID: 2 at filepath: .\blog_demo\wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd

InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.