• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Repair Kit Login Failed

ErrorHunter

New Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
Plesk Obsidian
Because of a mistake I wanted to use the repair kit with my access data, unfortunately it doesn't load
 
This is a typical error when the database server is not running. Did you check that, e.g. "systemctl status mariadb"?
 
Please check the output of the command systemctl status mariadb via SSH.
● mariadb.service - MariaDB 10.3.39 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: deactivating (stop-sigterm) (Result: exit-code)
Docs: man:mysqld(8)
systemd
Process: 13202 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 13203 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 13205 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status
Process: 13261 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Main PID: 13261 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
Tasks: 3 (limit: 1058)
Memory: 67.2M
CGroup: /system.slice/mariadb.service
└─731 /usr/sbin/mysqld

Oct 26 16:31:50 silly-benz.85-215-34-8.plesk.page systemd[1]: mariadb.service: Found left-over process 731 (mysqld) in control group while starting unit. Ignoring.
Oct 26 16:31:50 silly-benz.85-215-34-8.plesk.page systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 26 16:31:50 silly-benz.85-215-34-8.plesk.page systemd[1]: Starting MariaDB 10.3.39 database server...
Oct 26 16:31:50 silly-benz.85-215-34-8.plesk.page systemd[1]: mariadb.service: Found left-over process 731 (mysqld) in control group while starting unit. Ignoring.
Oct 26 16:31:50 silly-benz.85-215-34-8.plesk.page systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 26 16:32:26 silly-benz.85-215-34-8.plesk.page systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
 
You could either clean up the mysql related processes from the process tree or, might be easier, reboot.
 
I had exactly the same issue as topic starter on Ubuntu.
Suddenly all database interaction fails and mariadb cannot be restarted. Happend on multiple vps'ses.
Plesks repair function didn't work either. I had to reinstall everything and restore a backup.
 
Same problem here, can anyone help?

root@srv1 ~ # systemctl status mariadb


× mariadb.service - MariaDB 10.11.5 database server


Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)


Drop-In: /etc/systemd/system/mariadb.service.d


└─migrated-from-my.cnf-settings.conf


Active: failed (Result: exit-code) since Tue 2023-10-31 18:05:38 CET; 2s ago


Docs: man:mariadbd(8)


systemd


Process: 14164 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)


Process: 14165 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)


Process: 14167 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || ex>


Process: 14232 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)


Main PID: 14232 (code=exited, status=1/FAILURE)


Status: "MariaDB server is down"


CPU: 111ms





Oct 31 18:05:38 srv1.doitauto.de systemd[1]: Starting MariaDB 10.11.5 database server...


Oct 31 18:05:38 srv1.doitauto.de mariadbd[14232]: 2023-10-31 18:05:38 0 [Warning] Could not increase number of max_open_files to more than 32768 (request: 256450)


Oct 31 18:05:38 srv1.doitauto.de mariadbd[14232]: 2023-10-31 18:05:38 0 [Note] Starting MariaDB 10.11.5-MariaDB-1:10.11.5+maria~ubu2204 source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 14232


Oct 31 18:05:38 srv1.doitauto.de mariadbd[14232]: 2023-10-31 18:05:38 0 [ERROR] mariadbd: Error writing file './ddl_recovery.log' (Errcode: 28 "No space left on device")


Oct 31 18:05:38 srv1.doitauto.de mariadbd[14232]: 2023-10-31 18:05:38 0 [ERROR] Aborting


Oct 31 18:05:38 srv1.doitauto.de mariadbd[14232]: 2023-10-31 18:05:38 0 [ERROR] mariadbd: Error on close of '(null)' (Errcode: 9 "Bad file descriptor")


Oct 31 18:05:38 srv1.doitauto.de systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE


Oct 31 18:05:38 srv1.doitauto.de systemd[1]: mariadb.service: Failed with result 'exit-code'.


Oct 31 18:05:38 srv1.doitauto.de systemd[1]: Failed to start MariaDB 10.11.5 database server.
 
Error writing file './ddl_recovery.log' (Errcode: 28 "No space left on device")
Your disk space is exhausted. Please free disk space, then try to start the database server again.
 
Yes, that was the issue. Plesk was creating too many backups, and the hard drive was full. I deleted all the files under "dumps," and after that, Plesk started working again.
 
Back
Top