InnoDB: If you are attempting downgrade from MySQL 5.7.9 or later

: If you are attempting downgrade from 5.7.9 or later

这是一个版本问题,之前安装过mysql 5.7,再回到mariadb 5.5出现的问题。之后我搜了下网上很多人有这个问题。错误全文:

160916 17:03:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/
2016-09-16 17:03:22 139911928530976 [Note] /usr/sbin/mysqld (mysqld 10.1.17-) starting as process 16541 ...
2016-09-16 17:03:22 139911928530976 [Note] : Using mutexes to ref count buffer pool pages
2016-09-16 17:03:22 139911928530976 [Note] InnoDB: The InnoDB memory heap is disabled
2016-09-16 17:03:22 139911928530976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-09-16 17:03:22 139911928530976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2016-09-16 17:03:22 139911928530976 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-09-16 17:03:22 139911928530976 [Note] InnoDB: Using Linux native AIO
2016-09-16 17:03:22 139911928530976 [Note] InnoDB: Using SSE crc32 instructions
2016-09-16 17:03:22 139911928530976 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-09-16 17:03:22 139911928530976 [Note] InnoDB: Completed initialization of buffer pool
2016-09-16 17:03:22 139911928530976 [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
2016-09-16 17:03:22 139911928530976 [ERROR] Plugin 'InnoDB' init function returned error.
2016-09-16 17:03:22 139911928530976 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-09-16 17:03:22 139911928530976 [Note] Plugin 'FEEDBACK' is disabled.
2016-09-16 17:03:22 139911928530976 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-09-16 17:03:22 139911928530976 [ERROR] Aborting

160916 17:03:22 mysqld_safe mysqld from pid file /var/lib/mysql/iZ236priv51Z.pid ended

其中有一句是错误的“Unknown/unsupported storage engine: InnoDB”,这个其实在my.cnf已经配置过了,不知道是什么原因。

我们直接把以前版本的mysql全部卸载掉,只保留mariadb即可。

查出来有compat-mysql51.x86_64、mysql57-community-release.noarch将其卸载掉,这里我不确定perl-DBD-MySQL.x86_64是否与mariadb有关系,所以暂时不卸载。

其他网友也有类似的操作方法,参考文档:https://medium.com/@mcloide/moving-from-mysql-5-7-to-mariadb-10-1-c7cb042ed8d8#.un8u4nl5x

发布者

小旭旭

iOpenV 创始人,80后,从事:项目管理、网站建设方案、网站优化策略;职务:网站管理员、部门主管、技术总监、经理。

发表评论

电子邮件地址不会被公开。 必填项已用*标注