• 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
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Resolved Plesk won't start mariadb

Sysop

Basic Pleskian
We had a problem on our server and all the free space got used up, which caused mariadb to stop.

After freeing up the space and trying to access the Plesk Panel we are presented with:
Code:
DB query failed: SQLSTATE[HY000] [2002] No such file or directory
Trying to restart the mariadb process ends in a "Gateway Timeout"

Trying from the command-line:
Code:
$ systemctl enable mariadb
$ systemctl start mariadb
... hangs and does nothing ...
Checking with journal -xe:
Code:
systemd[1]: Got notification message from PID 12472, but reception only permitted for main PID which is currently not known
Attempting to repair:
Code:
$ plesk repair db -y
DB query failed: SQLSTATE[HY000] [2002] Connection refused
Trying to go one step further:
Code:
$ plesk repair installation
DB query failed: SQLSTATE[HY000] [2002] No such file or directory

We're dead in the water it seems, what now? Thanks
 
What kind of error messages in /var/log/mariadb/mariadb.log ?
 
I ended up killing the "mysql" process and restarting the service after that. For whatever reason the root user for the db was lost somehow. I had to re-create the user and did the repair installation again. It seems to be working fine now.

I would say that maybe the support document regarding this error could be updated with more information as to why it happens and how to resolve the problem perhaps, thanks.
 
Back
Top