Issue 500 Plesk\Exception\Database

[brontes]

Server operating system version

Ubuntu 20.04

Plesk version and microupdate number

18

I have this error when entering my site

Server Error

500 Plesk\Exception\Database​

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

Type	Plesk\Exception\Database
Message	DB query failed: SQLSTATE[HY000] [2002] No such file or directory
File	Mysql.php
Line	79

 

[Peter Debik]

Please find the details why MariaDB does not start in /var/log/syslog, e.g.
# grep mariadb /var/log/syslog
Normally you'll find a detailed explanation there why the database server won't start.

 

[brontes]

Please find the details why MariaDB does not start in /var/log/syslog, e.g.
# grep mariadb /var/log/syslog
Normally you'll find a detailed explanation there why the database server won't start.

Thanks for your time, here is my record

Jul 11 14:22:01 brave-wozniak systemd[1]: mariadb.service: Found left-over proce ss 1511 (mysqld) in control group while starting unit. Ignoring.
Jul 11 14:22:01 brave-wozniak systemd[1]: mariadb.service: Will not start SendSI GKILL=no service of type KillMode=control-group or mixed while processes exist
Jul 11 14:22:01 brave-wozniak systemd[1]: mariadb.service: Failed to run 'start- pre' task: Device or resource busy
Jul 11 14:22:01 brave-wozniak systemd[1]: mariadb.service: Failed with result 'r esources'.
Jul 11 14:22:06 brave-wozniak systemd[1]: mariadb.service: Found left-over proce ss 1511 (mysqld) in control group while starting unit. Ignoring.
Jul 11 14:22:06 brave-wozniak systemd[1]: mariadb.service: Will not start SendSI GKILL=no service of type KillMode=control-group or mixed while processes exist
Jul 11 14:22:06 brave-wozniak systemd[1]: mariadb.service: Failed to run 'start- pre' task: Device or resource busy
Jul 11 14:22:06 brave-wozniak systemd[1]: mariadb.service: Failed with result 'r esources'.
Jul 11 14:22:11 brave-wozniak systemd[1]: mariadb.service: Found left-over proce ss 1511 (mysqld) in control group while starting unit. Ignoring.
Jul 11 14:22:11 brave-wozniak systemd[1]: mariadb.service: Will not start SendSI GKILL=no service of type KillMode=control-group or mixed while processes exist
Jul 11 14:22:11 brave-wozniak systemd[1]: mariadb.service: Failed to run 'start- pre' task: Device or resource busy
Jul 11 14:22:11 brave-wozniak systemd[1]: mariadb.service: Failed with result 'r esources'.
Jul 11 14:22:14 brave-wozniak systemd[1]: mariadb.service: Got notification mess age from PID 1511, but reception only permitted for main PID which is currently not known

 

[Peter Debik]

The key is the "found left-over process in control group". This usually indicates unclean termination of a previous run, or service implementation deficiencies. This is normally caused by lack of disk space. The MySQL service cannot create temporary files when there is no free disk space limit has been reached on the root partition (or tmp partition if separated). Please check the disks space situation.

Example:

# df -h /var/lib/mysql /tmp
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 50G 50G 20K 100% /

Or maybe there are not enough inodes left:

# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
tmpfs 483902 1 483901 1% /dev/shm
/dev/sda3 3276800 3276800 0 100% /

If the disk space or inodes are at 100%, you could remove old temporary files, e.g.
# find /tmp -type f -mtime +14 -exec rm {} \;
# find /var/tmp -type f -mtime +14 -exec rm {} \;
# rm -rf /usr/local/psa/PMM/tmp/* /usr/local/psa/tmp/*

You could also clean the system from old package cache entries:
# du -sh /var/cache/apt/
# sudo apt-get clean

If this still does not help to clear enough disk space, let us know here, please.

 

[brontes]

df -h /var/lib/mysql /tmp
Filesystem Size Used Avail Use% Mounted on
/dev/md4 434G 322G 91G 79% /
/dev/md4 434G 322G 91G 79% /
root@brave-wozniak:~# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 4087353 594 4086759 1% /dev
tmpfs 4107130 1152 4105978 1% /run
/dev/md4 28942336 492705 28449631 2% /
tmpfs 4107130 1 4107129 1% /dev/shm
tmpfs 4107130 8 4107122 1% /run/lock
tmpfs 4107130 18 4107112 1% /sys/fs/cgroup
/dev/md2 121920 316 121604 1% /boot
/dev/loop0 11995 11995 0 100% /snap/core20/1974
/dev/loop1 12854 12854 0 100% /snap/core/15419
/dev/loop2 14327 14327 0 100% /snap/core22/806
/dev/loop3 11990 11990 0 100% /snap/core20/1950
/dev/loop4 14327 14327 0 100% /snap/core22/817
/dev/loop5 12906 12906 0 100% /snap/core/15511
/dev/loop7 936 936 0 100% /snap/lxd/25112
/dev/loop6 936 936 0 100% /snap/lxd/25086
overlay 28942336 492705 28449631 2% /var/lib/docker/overlay2/9d6596a85113fe3b64556f5c8fd4f06a65524c850955f9d9ae1e9169a161bcd8/merged
tmpfs 4107130 42 4107088 1% /run/user/0

 

[brontes]

I have cleaned the server and deleted data, but the same error continues. I have 100 /var/loops, can these be cleaned?

 

[Peter Debik]

I think that maybe some process is stuck so that cgroups cannot handle new MariaDB processes correctly. Would it be possible to reboot the server?

 

[brontes]

I think that maybe some process is stuck so that cgroups cannot handle new MariaDB processes correctly. Would it be possible to reboot the server?

Yes, I made the changes and restarted the server instantly. But the error persists

 

[Peter Debik]

I am not sure why cgroups is blocking something there. It's not really a Plesk issue, because that is not involved. Instead, before the database server even starts, it is blocked by another issue on the server. This probably needs to be checked on the server, unless someone here had exactly the same problem before and solved it.

You could try to ask Plesk support staff in a ticket on this, because they also know a lot about Linux in general. Pretty sure it needs to be investigated on the server.

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-

 

[brontes]

No estoy seguro de por qué cgroups está bloqueando algo allí. No es realmente un problema de Plesk, porque eso no está involucrado. En cambio, antes de que se inicie el servidor de la base de datos, se bloquea por otro problema en el servidor. Esto probablemente deba verificarse en el servidor, a menos que alguien aquí haya tenido exactamente el mismo problema antes y lo haya resuelto.

Podría intentar preguntarle al personal de soporte de Plesk en un ticket sobre esto, porque también saben mucho sobre Linux en general. Bastante seguro de que necesita ser investigado en el servidor.

Para iniciar sesión en soporte, vaya a https://support.plesk.com

Si experimenta problemas de inicio de sesión, consulte este artículo de KB:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

Si compró su licencia de un revendedor, su revendedor debe brindarle soporte. Si el revendedor no brinda soporte, aquí hay una alternativa:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-

Hello friend, I appreciate your time to read me, I had problems with the server and we reinstalled the server image before doing so, we downloaded the entire backup folder located in /var/lib/psa/dumps/domains/mydomain.com In total we have the backup of the last 3 days. The problem is that we have installed everything again and enabled Plesk again, but when uploading the backup through Plesk, I find an error. This only allows 2gb files when the one we have weighs 10gb we have all the files contained

 

[Dave W]

https://support.plesk.com/hc/en-us/articles/12377011223703-Cannot-upload-backup-file-bigger-than-2-GB-to-Plesk-Backup-Manager-Request-Entity-Too-Large