• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Failed to start MariaDB 10 database server

D

dline

New Pleskian
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.
 

Attachments

  • Screenshot 2023-05-01 at 00-07-36 Repair Kit.png
    Screenshot 2023-05-01 at 00-07-36 Repair Kit.png
    34.2 KB · Views: 9
Server Error

500 Plesk\Exception\Database​

DB query failed: SQLSTATE[HY000] [2002] No such file or directory
 
Strangelove said:
what's is in the output?
# journalctl -u mariadb
Click to expand...

-- 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 said:
and in /var/log/mysql/error.log ?
Click to expand...
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
 
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.
 
You must log in or register to reply here.

Similar threads

P
Resolved Upgrade Mariadb 10.3 to 10.6 completes but trying to start MariaDB fails with error "systemctl status mariadb.service" and "journalctl -xe"
Replies
13
Views
2K
PeterK900
P
R
Issue need help error mariadb
Replies
17
Views
2K
ramater
R
Talistech
Resolved Backups failing since a couple days: Unable to run the backup agent
Replies
1
Views
4K
Talistech
Talistech
J
Issue Error 500 Plesk\Exception\Database (DB query failed: SQLSTATE[HY000] [2002] Connection refused)
Replies
5
Views
421
Raul A.
R
AdrianC
Issue MariaDB High "created tmp disk tables"
Replies
9
Views
6K
AdrianC
AdrianC
Back
Top