• 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 Random temporary Database connection error across all Plesk sites

UnS3eN

Basic Pleskian
Server operating system version
Almalinux 8.10
Plesk version and microupdate number
18.0.69 #2
For a few weeks now we've been having this weird issue with all sites hosted on Plesk (except the pain one with no database) - all sites would suddenly show a database connections error until I restart mariadb service on Plesk. Even the ones with external DB server. It looks like a mysql.sock issue of some sort but there's nothing in the logs - both system and SQL, - and the service status is not showing anything out of ordinary when that heppens.
It sometime resolves itself ~20 minutes later without my involvement.
I can't figure out where else to look.
 
It sounds like all the database service connection slots get used up. By default, you should have 200 connections and 150 connections per user, so that no single user can use up all the connection slots.
Can you run the following when it happens?
Bash:
plesk db "show full processlist"
 
Back
Top