Question

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

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.

Answer 1

日志里面告诉你解决方法了。
1，确认basedir的权限问题
2，重新恢复数据库
3，配置文件中 加上 innodb_force_recovery = 4

一般情况下是解决方法3

Answer 2

xampp中的MySQL启动不了 日志在此 不过看不懂
日志里面告诉你解决方法了。
1，确认basedir的权限问题
2，重新恢复数据库
3，配置文件中 加上 innodb_force_recovery = 4

一般情况下是解决方法3

Answer 3

真正的完美解决办法：

1.修改my.cnf/my.ini ，innodb_force_recovery = 1

2.先启动Mysql，service mysql(d) start

3.修改my.cnf/my.ini ，innodb_force_recovery = 0

4.重新启动Mysql，service mysql(d) restart

5.导出出错的数据库  dump …dbname……sql(命令记不全了)，再删除这个出错的数据库

6.停止数据库service mysql stop

7.重启服务器

8.重启mysql（如果没有设置开机启动的话）

9.重启mysql后，导入之前备份的数据库，source sqlbak.sql。。。。额，大概意思是这样

10.再重启一下mysql试试，service mysql restart，嗯，能正常启动！

详见：网页链接

Answer 4

.\office\wp_terms.ibd
上面文件打不开了。文件要还在，运行一下check命令修复。