• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Problem with mariadb

FindYanot

New Pleskian
Hello all, i have a problem with maria db.
System: Centos 7 64

After DDOS attack, maria db does not start.
I reboot server and i got this error:

I tried "service mariadb restart"

Code:
May 10 18:05:39 hostname mariadb-prepare-db-dir[5195]: rm: cannot remove ‘/var/lib/mysql/domains/hostname/.discovered/backup_info_1704060007’: Permission denied
May 10 18:05:39 hostname mariadb-prepare-db-dir[5195]: rm: cannot remove ‘/var/lib/mysql/domains/hostname/.discovered/backup_info_1704070007’: Permission denied
May 10 18:05:39 hostname mariadb-prepare-db-dir[5195]: rm: cannot remove ‘/var/lib/mysql/domains/hostname/.discovered/backup_info_1703290007’: Permission denied
May 10 18:05:39 hostname mariadb-prepare-db-dir[5195]: rm: cannot remove ‘/var/lib/mysql/mysql.daily.dump.0.gz’: Permission denied
May 10 18:05:39 hostname mariadb-prepare-db-dir[5195]: rm: cannot remove ‘/var/lib/mysql/mysql.daily.dump.1.gz’: Permission denied
May 10 18:05:39 hostname mariadb-prepare-db-dir[5195]: rm: cannot remove ‘/var/lib/mysql/mysql.daily.dump.2.gz’: Permission denied
May 10 18:05:39 hostname systemd[1]: mariadb.service: control process exited, code=exited status=1
May 10 18:05:39 hostname systemd[1]: Failed to start MariaDB database server.
May 10 18:05:39 hostname systemd[1]: Unit mariadb.service entered failed state.
May 10 18:05:39 hostname systemd[1]: mariadb.service failed.

Server domain changed to "hostname".

How to fix it?
 
Last edited:
Hi FindYanot,

pls. make sure, that you add the corresponding VERSION, if you desire help for a third party software, which is supported by Plesk and the very first information should be always the output if the command "plesk version" ( logged in as user "root" over SSH ).


In some cases, the Plesk REPAIR UTILITY can help to solve issues ( => Plesk Repair Utility )

Example command:
Code:
plesk repair db -y -v
... where the option string "-y" can be as well replaced with "-n" to do a so called "dry-run", without any repairs. ;)
 
Back
Top