- Server operating system version
- Debian 12.5
- Plesk version and microupdate number
- 18.0.61 #5
Hello,
Last week I had different 5 plesk servers with the same problem. I see the error "too many connections" in the websites or control panel. All the servers are with Debian 12 and Plesk 18.0.61 #5
Restart mysql does not work. If I execute:
And I have to restart the server to fix the problem. If I restart the server instead of restart mysql I have to wait 30 minutes also.
There are 5 different servers this week with exactly the same problem so I think this could be a plesk problem. Before I open a bug ticket I want to know if someone is facing the same problem or if you know how to prevent it.
Thank you.
Last week I had different 5 plesk servers with the same problem. I see the error "too many connections" in the websites or control panel. All the servers are with Debian 12 and Plesk 18.0.61 #5
Restart mysql does not work. If I execute:
I have to wait nearly 30 minutes and after that mysql is stopped but not started.sudo service mysql restart || service mariadb restart || service mysqld restart
Job for mariadb.service failed because of unavailable resources or another system error.
See "systemctl status mariadb.service" and "journalctl -xeu mariadb.service" for details.
root@server:/home/usr# journalctl -xeu mariadb.service
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599102 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599101 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599100 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599099 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599098 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599097 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599096 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599095 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599094 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599093 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599092 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599091 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599089 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599088 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599086 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599085 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599081 (user : 'hedKrwp75052619') did not exit
jun 16 22:05:38 dv23 mariadbd[930]: 2024-06-16 22:05:38 0 [Warning] /usr/sbin/mariadbd: Thread 2599080 (user : 'hedKrwp75052619') did not exit
jun 16 22:20:18 dv23 systemd[1]: mariadb.service: State 'stop-sigterm' timed out. Skipping SIGKILL.
jun 16 22:35:18 dv23 systemd[1]: mariadb.service: State 'final-sigterm' timed out. Skipping SIGKILL. Entering failed mode.
jun 16 22:35:18 dv23 systemd[1]: mariadb.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ The unit mariadb.service has entered the 'failed' state with result 'timeout'.
jun 16 22:35:18 dv23 systemd[1]: mariadb.service: Unit process 930 (mariadbd) remains running after unit stopped.
jun 16 22:35:18 dv23 systemd[1]: Stopped mariadb.service - MariaDB 10.11.6 database server.
░░ Subject: A stop job for unit mariadb.service has finished
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ A stop job for unit mariadb.service has finished.
░░
░░ The job identifier is 1083555 and the job result is done.
jun 16 22:35:18 dv23 systemd[1]: mariadb.service: Consumed 2d 20h 25min 25.944s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ The unit mariadb.service completed and consumed the indicated resources.
jun 16 22:35:57 dv23 systemd[1]: mariadb.service: Found left-over process 930 (mariadbd) in control group while starting unit. Ignoring.
jun 16 22:35:57 dv23 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
jun 16 22:35:57 dv23 systemd[1]: mariadb.service: Will not start SendSIGKILL=no service of type KillMode=control-group or mixed while processes exist
jun 16 22:35:57 dv23 systemd[1]: mariadb.service: Failed to run 'start-pre' task: Device or resource busy
jun 16 22:35:57 dv23 systemd[1]: mariadb.service: Failed with result 'resources'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ The unit mariadb.service has entered the 'failed' state with result 'resources'.
jun 16 22:35:57 dv23 systemd[1]: mariadb.service: Unit process 930 (mariadbd) remains running after unit stopped.
jun 16 22:35:57 dv23 systemd[1]: Failed to start mariadb.service - MariaDB 10.11.6 database server.
░░ Subject: A start job for unit mariadb.service has failed
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ A start job for unit mariadb.service has finished with a failure.
░░
░░ The job identifier is 1083785 and the job result is failed.
And I have to restart the server to fix the problem. If I restart the server instead of restart mysql I have to wait 30 minutes also.
There are 5 different servers this week with exactly the same problem so I think this could be a plesk problem. Before I open a bug ticket I want to know if someone is facing the same problem or if you know how to prevent it.
Thank you.