mysql启动时提示1067错误

[willieso]

之前学习java的时候装了mysql.5.7.17，使用的是3306端口，配置了环境变量。最近装了xampp但是无法启动其集成的mysql，端口改成了3308，注册表和my.ini文件都已修改，但是开启时仍然提示1067错误。试过很多办法都不行，求解谢谢！

[二月十六]

看看错误日志说什么

[willieso]

2017-04-10 22:18:35 1df4 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. 2017-04-10 22:18:35 7668 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB. 2017-04-10 22:18:35 7668 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-04-10 22:18:35 7668 [Note] InnoDB: The InnoDB memory heap is disabled 2017-04-10 22:18:35 7668 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2017-04-10 22:18:35 7668 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2017-04-10 22:18:35 7668 [Note] InnoDB: Compressed tables use zlib 1.2.3 2017-04-10 22:18:35 7668 [Note] InnoDB: Using generic crc32 instructions 2017-04-10 22:18:35 7668 [Note] InnoDB: Initializing buffer pool, size = 16.0M 2017-04-10 22:18:35 7668 [Note] InnoDB: Completed initialization of buffer pool 2017-04-10 22:18:36 7668 [Note] InnoDB: Highest supported file format is Barracuda. InnoDB: No valid checkpoint found. InnoDB: If you are attempting downgrade from MySQL 5.7.9 or later, InnoDB: please refer to http://dev.mysql.com/doc/refman/5.6/en/upgrading-downgrading.html InnoDB: If this error appears when you are creating an InnoDB database, InnoDB: the problem may be that during an earlier attempt you managed InnoDB: to create the InnoDB data files, but log file creation failed. InnoDB: If that is the case, please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html 2017-04-10 22:18:36 7668 [ERROR] Plugin 'InnoDB' init function returned error. 2017-04-10 22:18:36 7668 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2017-04-10 22:18:36 7668 [Note] Plugin 'FEEDBACK' is disabled. 2017-04-10 22:18:36 7668 [ERROR] Unknown/unsupported storage engine: InnoDB 2017-04-10 22:18:36 7668 [ERROR] Aborting

[二月十六]

引用 2楼我是你的主体 的回复:

2017-04-10 22:18:35 1df4 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. 2017-04-10 22:18:35 7668 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB. 2017-04-10 22:18:35 7668 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-04-10 22:18:35 7668 [Note] InnoDB: The InnoDB memory heap is disabled 2017-04-10 22:18:35 7668 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2017-04-10 22:18:35 7668 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2017-04-10 22:18:35 7668 [Note] InnoDB: Compressed tables use zlib 1.2.3 2017-04-10 22:18:35 7668 [Note] InnoDB: Using generic crc32 instructions 2017-04-10 22:18:35 7668 [Note] InnoDB: Initializing buffer pool, size = 16.0M 2017-04-10 22:18:35 7668 [Note] InnoDB: Completed initialization of buffer pool 2017-04-10 22:18:36 7668 [Note] InnoDB: Highest supported file format is Barracuda. InnoDB: No valid checkpoint found. InnoDB: If you are attempting downgrade from MySQL 5.7.9 or later, InnoDB: please refer to http://dev.mysql.com/doc/refman/5.6/en/upgrading-downgrading.html InnoDB: If this error appears when you are creating an InnoDB database, InnoDB: the problem may be that during an earlier attempt you managed InnoDB: to create the InnoDB data files, but log file creation failed. InnoDB: If that is the case, please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html 2017-04-10 22:18:36 7668 [ERROR] Plugin 'InnoDB' init function returned error. 2017-04-10 22:18:36 7668 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2017-04-10 22:18:36 7668 [Note] Plugin 'FEEDBACK' is disabled. 2017-04-10 22:18:36 7668 [ERROR] Unknown/unsupported storage engine: InnoDB 2017-04-10 22:18:36 7668 [ERROR] Aborting

这会儿百度错误信息应该能解决了吧

[willieso]

引用 3 楼 sinat_28984567 的回复:

[quote=引用 2楼我是你的主体 的回复:]2017-04-10 22:18:35 1df4 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. 2017-04-10 22:18:35 7668 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB. 2017-04-10 22:18:35 7668 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-04-10 22:18:35 7668 [Note] InnoDB: The InnoDB memory heap is disabled 2017-04-10 22:18:35 7668 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2017-04-10 22:18:35 7668 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2017-04-10 22:18:35 7668 [Note] InnoDB: Compressed tables use zlib 1.2.3 2017-04-10 22:18:35 7668 [Note] InnoDB: Using generic crc32 instructions 2017-04-10 22:18:35 7668 [Note] InnoDB: Initializing buffer pool, size = 16.0M 2017-04-10 22:18:35 7668 [Note] InnoDB: Completed initialization of buffer pool 2017-04-10 22:18:36 7668 [Note] InnoDB: Highest supported file format is Barracuda. InnoDB: No valid checkpoint found. InnoDB: If you are attempting downgrade from MySQL 5.7.9 or later, InnoDB: please refer to http://dev.mysql.com/doc/refman/5.6/en/upgrading-downgrading.html InnoDB: If this error appears when you are creating an InnoDB database, InnoDB: the problem may be that during an earlier attempt you managed InnoDB: to create the InnoDB data files, but log file creation failed. InnoDB: If that is the case, please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html 2017-04-10 22:18:36 7668 [ERROR] Plugin 'InnoDB' init function returned error. 2017-04-10 22:18:36 7668 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2017-04-10 22:18:36 7668 [Note] Plugin 'FEEDBACK' is disabled. 2017-04-10 22:18:36 7668 [ERROR] Unknown/unsupported storage engine: InnoDB 2017-04-10 22:18:36 7668 [ERROR] Aborting

这会儿百度错误信息应该能解决了吧[/quote] 好的，谢谢了！我去看一下

[willieso]

引用 5 楼 lamking 的回复:

InnoDB: No valid checkpoint found. 最初的错误是这个，造成这个的原因，通常是ib_log文件出问题了。或者是你只删掉了ib_log*文件，没删ibdata，或者是ib_log文件坏掉了或是被清空了。看看最近有没有对这些文件进行操作吧

大概就是log文件出问题了，但是好像没看到ibdata。我把目录下的log文件删掉以后，mysql可以正常启动了

[lamking]

InnoDB: No valid checkpoint found. 最初的错误是这个，造成这个的原因，通常是ib_log文件出问题了。或者是你只删掉了ib_log*文件，没删ibdata，或者是ib_log文件坏掉了或是被清空了。看看最近有没有对这些文件进行操作吧

[willieso]

引用 7 楼 zhujinqiang 的回复:

InnoDB: No valid checkpoint found. 你的log文件出了问题，将innodb的ib_logfile*都删除掉之后，重启MySQL. 如果还不启动的就去删除ibdata*，之后重新建库吧。 因为innodb的数据是存储在ibdata*文件里的，如果保留ibdata*但将ib_logfile*都删除掉的话，mysql还是启动不了，会报错no valid checkpoint found,这是因为innodb是支持事务的，启动之后，MYSQL需要一些前滚和回滚的操作， 以保证事务的一致性，但ib_logfile*被删除之后，无法保障事务的一致性，最终结果导致MYSQL无法启动。

好的谢谢！删除log文件以后问题解决了，现在mysql可以正常启动

[zhujinqiang]

InnoDB: No valid checkpoint found. 你的log文件出了问题，将innodb的ib_logfile*都删除掉之后，重启MySQL. 如果还不启动的就去删除ibdata*，之后重新建库吧。 因为innodb的数据是存储在ibdata*文件里的，如果保留ibdata*但将ib_logfile*都删除掉的话，mysql还是启动不了，会报错no valid checkpoint found,这是因为innodb是支持事务的，启动之后，MYSQL需要一些前滚和回滚的操作， 以保证事务的一致性，但ib_logfile*被删除之后，无法保障事务的一致性，最终结果导致MYSQL无法启动。