So you have a nice wordpress (or similar site) running, but then all of a sudden you got a nasty message telling you that, the InnobDB registration as a storage engine failed.<\/p>\n
\r\n# tail \/var\/log\/mariadb\/mariadb.log\r\nInnoDB: If that is the case, please refer to\r\nInnoDB: http:\/\/dev.mysql.com\/doc\/refman\/5.5\/en\/error-creating-innodb.html\r\n160914 6:45:29 [ERROR] Plugin 'InnoDB' init function returned error.\r\n160914 6:45:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.\r\n160914 6:45:29 [ERROR] Failed to initialize plugins.\r\n160914 6:45:29 [ERROR] Aborting\r\n<\/pre>\n\r\n160914 6:45:29 [Note] \/usr\/libexec\/mysqld: Shutdown complete\r\n\r\n160914 06:45:29 mysqld_safe mysqld from pid file \/var\/lib\/mysql\/wpstack.localdomain.pid ended\r\n\r\n# systemctl status mariadb\r\n\u25cf mariadb.service - MariaDB database server\r\n Loaded: loaded (\/usr\/lib\/systemd\/system\/mariadb.service; enabled; vendor preset: disabled)\r\n Drop-In: \/etc\/systemd\/system\/mariadb.service.d\r\n \u2514\u2500limits.conf\r\n Active: failed (Result: exit-code) since Wed 2016-09-14 06:25:38 UTC; 2min 32s ago\r\n Process: 1434 ExecStartPost=\/usr\/libexec\/mariadb-wait-ready $MAINPID (code=exited, status=1\/FAILURE)\r\n Process: 1433 ExecStart=\/usr\/bin\/mysqld_safe --basedir=\/usr (code=exited, status=0\/SUCCESS)\r\n Process: 1305 ExecStartPre=\/usr\/libexec\/mariadb-prepare-db-dir %n (code=exited, status=0\/SUCCESS)\r\n Main PID: 1433 (code=exited, status=0\/SUCCESS)\r\n\r\nSep 14 06:25:35 wpstack.localdomain systemd[1]: Starting MariaDB database se....\r\nSep 14 06:25:37 wpstack.localdomain mysqld_safe[1433]: 160914 06:25:37 mysqld...\r\nSep 14 06:25:37 wpstack.localdomain mysqld_safe[1433]: 160914 06:25:37 mysqld...\r\nSep 14 06:25:38 wpstack.localdomain systemd[1]: mariadb.service: control pro...1\r\nSep 14 06:25:38 wpstack.localdomain systemd[1]: Failed to start MariaDB data....\r\nSep 14 06:25:38 wpstack.localdomain systemd[1]: Unit mariadb.service entered....\r\nSep 14 06:25:38 wpstack.localdomain systemd[1]: mariadb.service failed.\r\nHint: Some lines were ellipsized, use -l to show in full.\r\n[root@wpstack ~]# systemctl start mariadb\r\nJob for mariadb.service failed because the control process exited with error code. See \"systemctl status mariadb.service\" and \"journalctl -xe\" for details.\r\n[root@wpstack ~]# systemctl start mariadb\r\nJob for mariadb.service failed because the control process exited with error code. See \"systemctl status mariadb.service\" and \"journalctl -xe\" for details.\r\n\r\n<\/pre>\nThis is naturally a problem since until it is resolved you have no database service running. It is fairly easy to resolve in most cases, by removing the log from var\/lib\/mysql<\/p>\n
\r\nmv \/var\/lib\/mysql\/ib_logfile0{,.bak} \t \t \t \r\nmv \/var\/lib\/mysql\/ib_logfile1{,.bak} \t \t \t \r\nmv \/var\/lib\/mysql\/ibdata1{,.bak} \r\n<\/pre>\nThese simply move the files away, which allows InnoDB to continue operating. Please note that this may not always fix your issue and in some situations might result in data loss, so it is advisable to take a backup of the database filesystem before proceeding.<\/p>\n","protected":false},"excerpt":{"rendered":"
So you have a nice wordpress (or similar site) running, but then all of a sudden you got a nasty message telling you that, the InnobDB registration as a storage engine failed. # tail \/var\/log\/mariadb\/mariadb.log InnoDB: If that is the … Continue reading