• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved DB query failed: SQLSTATE[HY000] [2002] No such file or directory mariadb cant start

emreboy

New Pleskian
Server operating system version
ubuntu 22
Plesk version and microupdate number
18.0.58
i cant login plesk and i have error. On repair screen maridab service cant stopped. i cant restart it.
i am licenced user but wait for support 2 hour. i have important db so cant fresh mariadb install
Can anyone help me?
i run
Code:
root@srv:/# systemctl restart mariadb

Job for mariadb.service failed because the control process exited with error code.

See "systemctl status mariadb.service" and "journalctl -xeu mariadb.service" for details.

and

Code:
root@srv:/# systemctl status mysql.service -l
× mariadb.service - MariaDB 10.6.12 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2024-01-22 09:28:31 CET; 1min 52s ago
       Docs: man:mariadbd(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 10882 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 10883 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 10885 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   &>
    Process: 10905 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 10905 (code=exited, status=1/FAILURE)
     Status: "MariaDB server is down"
        CPU: 117ms

Jan 22 09:28:30 srv.pluvien.com mariadbd[10905]: 2024-01-22  9:28:30 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
Jan 22 09:28:30 srv.pluvien.com mariadbd[10905]: 2024-01-22  9:28:30 0 [Note] InnoDB: Starting shutdown...
Jan 22 09:28:31 srv.pluvien.com mariadbd[10905]: 2024-01-22  9:28:31 0 [ERROR] Plugin 'InnoDB' init function returned error.
Jan 22 09:28:31 srv.pluvien.com mariadbd[10905]: 2024-01-22  9:28:31 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jan 22 09:28:31 srv.pluvien.com mariadbd[10905]: 2024-01-22  9:28:31 0 [Note] Plugin 'FEEDBACK' is disabled.
Jan 22 09:28:31 srv.pluvien.com mariadbd[10905]: 2024-01-22  9:28:31 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Jan 22 09:28:31 srv.pluvien.com mariadbd[10905]: 2024-01-22  9:28:31 0 [ERROR] Aborting
Jan 22 09:28:31 srv.pluvien.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 09:28:31 srv.pluvien.com systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jan 22 09:28:31 srv.pluvien.com systemd[1]: Failed to start MariaDB 10.6.12 database server.
 

Attachments

  • Ekran görüntüsü 2024-01-22 112249.png
    Ekran görüntüsü 2024-01-22 112249.png
    294.6 KB · Views: 8
  • 2.png
    2.png
    109.5 KB · Views: 8
Support solve my problem here is solution:


Code:
Thank you for your reply.
Yes, you are correct, the issue is resolved, MariaDB is up and running.

 

It was failing to start with this error:

Jan 22 11:02:07 srv.pluvien.com mariadbd[20245]: 2024-01-22 11:02:07 0 [ERROR] InnoDB: Malformed log record; set innodb_force_recovery=1 to ignore.



The cause of that error is that the MariaDB log file was corrupted, so I have renamed it and after that, MariaDB was started successfully:



root@srv:~# mv /var/lib/mysql/ib_logfile0 /var/lib/mysql/ib_logfile0.bak

root@srv:~# systemctl start mariadb.service

root@srv:~# systemctl status mariadb.service

● mariadb.service - MariaDB 10.6.12 database server


...
 
Back
Top