Question Failed to start MariaDB 10 database server

[dline]

Server operating system version

debian 9.0

Plesk version and microupdate number

Obsidian 18.0.44

Unable to start mariadb service. when i tried to repair the result did not change.
The first cause of the problem was that mariadb could not be started because the server disk capacity was full.
After deleting the logs, disk space was freed, but mysqld.sock continued to give an error because there was no file.

 

[dline]

Server Error

500 Plesk\Exception\Database​

DB query failed: SQLSTATE[HY000] [2002] No such file or directory

 

[Strangelove]

what's is in the output?
# journalctl -u mariadb

 

[dline]

what's is in the output?
# journalctl -u mariadb

-- Logs begin at Mon 2023-05-01 10:05:13 +03, end at Mon 2023-05-01 10:33:38 +03. --
May 01 10:05:14 server.abc.com systemd[1]: Starting MariaDB 10.1.48 database server...
May 01 10:05:15 server.abc.com mysqld[1796]: 2023-05-01 10:05:15 140621889342848 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB
-0+deb9u2) starting as process 1796 ...
May 01 10:05:17 server.abc.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
May 01 10:05:17 server.abc.com systemd[1]: Failed to start MariaDB 10.1.48 database server.
May 01 10:05:17 server.abc.com systemd[1]: mariadb.service: Unit entered failed state.
May 01 10:05:17 server.abc.com systemd[1]: mariadb.service: Failed with result 'exit-code'.
May 01 10:05:22 server.abc.com systemd[1]: Starting MariaDB 10.1.48 database server...
May 01 10:05:23 server.abc.com mysqld[2730]: 2023-05-01 10:05:23 140062909783424 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB
-0+deb9u2) starting as process 2730 ...
May 01 10:05:25 server.abc.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
May 01 10:05:25 server.abc.com systemd[1]: Failed to start MariaDB 10.1.48 database server.
May 01 10:05:25 server.abc.com systemd[1]: mariadb.service: Unit entered failed state.
May 01 10:05:25 server.abc.com systemd[1]: mariadb.service: Failed with result 'exit-code'.
May 01 10:05:29 server.abc.com systemd[1]: Starting MariaDB 10.1.48 database server...
May 01 10:05:30 server.abc.com mysqld[2936]: 2023-05-01 10:05:30 140076186107264 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB
-0+deb9u2) starting as process 2936 ...
May 01 10:05:32 server.abc.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
May 01 10:05:32 server.abc.com systemd[1]: Failed to start MariaDB 10.1.48 database server.
May 01 10:05:32 server.abc.com systemd[1]: mariadb.service: Unit entered failed state.
May 01 10:05:32 server.abc.com systemd[1]: mariadb.service: Failed with result 'exit-code'.
May 01 10:05:37 server.abc.com systemd[1]: Starting MariaDB 10.1.48 database server...
May 01 10:05:38 server.abc.com mysqld[3143]: 2023-05-01 10:05:38 140542810709376 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB
-0+deb9u2) starting as process 3143 ...
May 01 10:05:39 server.abc.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
May 01 10:05:39 server.abc.com systemd[1]: Failed to start MariaDB 10.1.48 database server.
May 01 10:05:39 server.abc.com systemd[1]: mariadb.service: Unit entered failed state.
May 01 10:05:39 server.abc.com systemd[1]: mariadb.service: Failed with result 'exit-code'.
May 01 10:05:44 server.abc.com systemd[1]: Starting MariaDB 10.1.48 database server...
May 01 10:05:45 server.abc.com mysqld[3342]: 2023-05-01 10:05:45 140643041148288 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB
-0+deb9u2) starting as process 3342 ...
May 01 10:05:47 server.abc.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
May 01 10:05:47 server.abc.com systemd[1]: Failed to start MariaDB 10.1.48 database server.
May 01 10:05:47 server.abc.com systemd[1]: mariadb.service: Unit entered failed state.
May 01 10:05:47 server.abc.com systemd[1]: mariadb.service: Failed with result 'exit-code'.
May 01 10:05:52 server.abc.com systemd[1]: Starting MariaDB 10.1.48 database server...
May 01 10:05:53 server.abc.com mysqld[3607]: 2023-05-01 10:05:53 139887951363456 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB
-0+deb9u2) starting as process 3607 ...

 

[Strangelove]

and in /var/log/mysql/error.log ?

 

[dline]

and in /var/log/mysql/error.log ?

I do not have this directory. /var/log/mysql/error.log

/var/log/mysql/mysql.log
/usr/sbin/mysqld, Version: 10.1.48-MariaDB-0+deb9u2 (Debian 9.13). started with:
Tcp port: 3306 Unix socket: /var/run/mysqld/mysqld.sock
Time Id Command Argument
/usr/sbin/mysqld, Version: 10.1.48-MariaDB-0+deb9u2 (Debian 9.13). started with:
Tcp port: 3306 Unix socket: /var/run/mysqld/mysqld.sock
Time Id Command Argument
/usr/sbin/mysqld, Version: 10.1.48-MariaDB-0+deb9u2 (Debian 9.13). started with:
Tcp port: 3306 Unix socket: /var/run/mysqld/mysqld.sock
Time Id Command Argument

/var/log/mysql/mysql.err
2023-05-01 10:47:16 140518479482240 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2023-05-01 10:47:16 140518479482240 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2023-05-01 10:47:16 140518479482240 [Note] InnoDB: The InnoDB memory heap is disabled
2023-05-01 10:47:16 140518479482240 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-05-01 10:47:16 140518479482240 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-05-01 10:47:16 140518479482240 [Note] InnoDB: Compressed tables use zlib 1.2.8
2023-05-01 10:47:16 140518479482240 [Note] InnoDB: Using Linux native AIO
2023-05-01 10:47:16 140518479482240 [Note] InnoDB: Using SSE crc32 instructions
2023-05-01 10:47:16 140518479482240 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-05-01 10:47:16 140518479482240 [Note] InnoDB: Completed initialization of buffer pool
2023-05-01 10:47:16 140518479482240 [ERROR] InnoDB: Cannot create log files because data files are corrupt or the database was not shut down cleanly after creating the data files.
2023-05-01 10:47:16 140518479482240 [ERROR] Plugin 'InnoDB' init function returned error.
2023-05-01 10:47:16 140518479482240 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-05-01 10:47:16 140518479482240 [Note] Plugin 'FEEDBACK' is disabled.
2023-05-01 10:47:16 140518479482240 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2023-05-01 10:47:16 140518479482240 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-05-01 10:47:16 140518479482240 [ERROR] Aborting

 

[Strangelove]

Looks like time for https://support.plesk.com/hc/en-us/articles/12377798484375 then

 

[dline]

Looks like time for https://support.plesk.com/hc/en-us/articles/12377798484375 then

I followed the steps in the link, the mariadb service was fixed, but it gives the following error.

500 Plesk\Exception\Database
DB query failed: SQLSTATE[HY000] [1049] Unknown database 'psa'

 

[Strangelove]

It's expected and it's needed to follow all the article's steps.
Dumped databases need to be restored after the MariaDB was re-initialized.