Mysql not starting

Revision as of 14:12, 22 August 2022 by Amolmistry (talk | contribs) (MySQL not starting throwing error "Unknown/unsupported storage engine: InnoDB")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

MySQL not starting throwing error "Unknown/unsupported storage engine: InnoDB"


   KB 24464        Last updated on 2022-08-22  




0.00
(0 votes)


Problem

Whwn MySQL not starting and throwing below error. "Unknown/unsupported storage engine: InnoDB"

220821 20:42:34 mysqld_safe Starting mysqld daemon with databases from /opt/zimbra/db/data
2022-08-21 20:42:34 140450186807168 [Note] /opt/zimbra/common/sbin/mysqld (mysqld 10.1.25-MariaDB) starting as process 99524 ...
2022-08-21 20:42:34 140450186807168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-08-21 20:42:34 140450186807168 [Note] InnoDB: The InnoDB memory heap is disabled
2022-08-21 20:42:34 140450186807168 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-08-21 20:42:34 140450186807168 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-08-21 20:42:34 140450186807168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2022-08-21 20:42:34 140450186807168 [Note] InnoDB: Using Linux native AIO
2022-08-21 20:42:34 140450186807168 [Note] InnoDB: Using SSE crc32 instructions
2022-08-21 20:42:34 140450186807168 [Note] InnoDB: Initializing buffer pool, size = 5.5G
2022-08-21 20:42:35 140450186807168 [Note] InnoDB: Completed initialization of buffer pool
2022-08-21 20:42:35 140450186807168 [Note] InnoDB: Highest supported file format is Barracuda.
InnoDB: Set innodb_force_recovery to ignore this error.
2022-08-21 20:42:35 140450186807168 [ERROR] Plugin 'InnoDB' init function returned error.
2022-08-21 20:42:35 140450186807168 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-08-21 20:42:35 140450186807168 [Note] Plugin 'FEEDBACK' is disabled.
2022-08-21 20:42:35 140450186807168 [ERROR] Unknown/unsupported storage engine: InnoDB
2022-08-21 20:42:35 140450186807168 [ERROR] Aborting

Solution

The issue usually occurred due to the following corrupted log files stored under /opt/zimbra/db/data

ib_logfile0
ib_logfile1

Upon moving/deleting these files, the issue will resolve.

su - zimbra
cd /opt/zimbra/db/data

mv ib_logfile0 /tmp/.
mv ib_logfile1 /tmp/.

or 

rm ib_logfile0
rm ib_logfile1

Now try starting the MySQL and it should start

mysql.server start
Submitted by: Amol Mistry
Jump to: navigation, search