xampp mysql 日志_xampp中的MySQL启动不了 日志在此 不过看不懂

2014-09-0221:47:24288[Note]Plugin'FEDERATED'isdisabled.2014-09-0221:47:241c78InnoDB:Warning:Usinginnodb_additional_mem_pool_sizeisDEPRECATED.Thisoptionmayberemovedinfutur...

2014-09-02 21:47:24 288 [Note] Plugin 'FEDERATED' is disabled.

2014-09-02 21:47:24 1c78 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.

2014-09-02 21:47:24 288 [Note] InnoDB: The InnoDB memory heap is disabled

2014-09-02 21:47:24 288 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2014-09-02 21:47:24 288 [Note] InnoDB: Compressed tables use zlib 1.2.3

2014-09-02 21:47:24 288 [Note] InnoDB: Not using CPU crc32 instructions

2014-09-02 21:47:24 288 [Note] InnoDB: Initializing buffer pool, size = 16.0M

2014-09-02 21:47:24 288 [Note] InnoDB: Completed initialization of buffer pool

2014-09-02 21:47:24 288 [Note] InnoDB: Highest supported file format is Barracuda.

2014-09-02 21:47:24 288 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 3043140 in the ib_logfiles!

2014-09-02 21:47:24 288 [Note] InnoDB: Database was not shutdown normally!

2014-09-02 21:47:24 288 [Note] InnoDB: Starting crash recovery.

2014-09-02 21:47:24 288 [Note] InnoDB: Reading tablespace information from the .ibd files...

2014-09-02 21:47:24 288 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace office/wp_terms which uses space ID: 3 at filepath: .\office\wp_terms.ibd

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

展开