伙计们我用mysql yday安装了xampp。设法用一个表创建一个简单的数据库。
今天早上，由于某种原因，Apache在我的控制面板中运行，但是mysql出现了“错误：mySQL Shoudown意外”。阅读日志，显然有些“innodb_table_stats”无法找到/到达。如果它有帮助，我正在玩my.cnf，正如这里所讨论的那样（MySQL Server has gone away when importing large sql file）yday。
关注完整日志。
2013-12-05 09:18:16 2660 [Note] Plugin 'FEDERATED' is disabled.
2013-12-05 09:18:16 124c 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-12-05 09:18:16 2660 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-05 09:18:16 2660 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-05 09:18:16 2660 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-05 09:18:16 2660 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-05 09:18:16 2660 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-05 09:18:16 2660 [Note] InnoDB: Completed initialization of buffer pool
2013-12-05 09:18:16 2660 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-05 09:18:16 2660 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 5602287 in the ib_logfiles!
2013-12-05 09:18:16 2660 [Note] InnoDB: Database was not shutdown normally!
2013-12-05 09:18:16 2660 [Note] InnoDB: Starting crash recovery.
2013-12-05 09:18:16 2660 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-05 09:18:17 2660 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace intrasdata@00201@002e0@002e0/intrasextract uses space ID: 2 at filepath: .\intrasdata@00201@002e0@002e0\intrasextract.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.
答案 0 :(得分：0)
我会再次重新安装mysql服务器，或者如果它更容易重新安装xampp。