• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Aborted connection 0 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (Too many connections)

  • Thread starter Deleted member 209767
  • Start date
D

Deleted member 209767

Guest
Server operating system version
AlmaLinux
Plesk version and microupdate number
last
We have 2 servers crashing intermittently with all sites down until we restart MySQL

In the logs, there are hundreds of errors like this just before the downtime:

2023-05-05 5:57:15 0 [Warning] Aborted connection 0 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (Too many connections)

What could be causing this? How can I debug this issue?
 
What is your database version? Cause searching the web there appears to have been a known issue that was patched in a later release.
 
One server is running MariaDB 10.3 and the other one 10.5
I will try upgrading it and see if it helps
 
"Too many connections" could also simply be caused by too many concurrent connections. This happens when either too many users connect at the same time or if scripts create persistent database connections (they open one but never close it again). You can set two important parameters in the [mysqld] section of /etc/my.cnf:

max_connections=<some high integer number, e.g. 2000>
max_user_connections=<some low integer number, e.g. 100>

Then restart the database server for these settings to take effect. Most often the max_user_connections set to a low number will keep your server available, because it will keep single users from occupying all possible connections to the database server. If the user reaches his personal limit, he won't be able to add another connection, but other users will. You can check the connections simply by looking at the database processlist (>show processlist), there you will see which user is doing what.
 
Back
Top