error in mariadb
systemctl status mariadb.service
● mariadb.service - MariaDB 10.3.37 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Sun 2025-02-16 23:04:19 WIB; 2min 48s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 29867 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 29855 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 29852 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 29867 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
Feb 16 23:04:19 mysqld[29867]: 2025-02-16 23:04:19 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Feb 16 23:04:19 mysqld[29867]: 2025-02-16 23:04:19 0 [Note] Plugin 'FEEDBACK' is disabled.
Feb 16 23:04:19 mysqld[29867]: 2025-02-16 23:04:19 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
Feb 16 23:04:19 mysqld[29867]: 2025-02-16 23:04:19 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Feb 16 23:04:19 mysqld[29867]: 2025-02-16 23:04:19 0 [ERROR] Aborting
Feb 16 23:04:19 mysqld[29867]: Warning: Memory not freed: 520
Feb 16 23:04:19 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Feb 16 23:04:19 systemd[1]: Failed to start MariaDB 10.3.37 database server.
Feb 16 23:04:19 systemd[1]: Unit mariadb.service entered failed state.
Feb 16 23:04:19 systemd[1]: mariadb.service failed.
-
Hey there! Unfortunately this error usually indicates there is corruption on the system with the InnoDB tables and MySQL can only be started if "innodb_force_recovery=1" is added to the MySQL configuration.
The best information we have on this issue can be found here:
https://support.cpanel.net/hc/en-us/articles/1500006010582-InnoDB-Corruption-Repair-Guide
but you'll likely need to work with a professional MySQL admin to limit data loss.
0
Please sign in to leave a comment.
Comments
1 comment