• 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.

mchk still has error after first big fix

R

rvdmeer

Guest
Hi there,

Oke, the last bug was an segmentation failed in mchk. After they fixed this i guess the programmer forgot to close the mysql connection to the PSA database.

[root@vite plugins]# /usr/local/psa/admin/bin/mchk -v
mchk: db_connect: failed to connect to database: Error: Too many connections
mchk: db_connect: failed to connect to database: Error: Too many connections
mchk: Unable to connect to the Plesk database
mchk: Unable to connect to the Plesk database

I guess more users are experiencing this... is there any news regarding this issue?

Kind regards,
 
This is easily fixed by increasing the max connections for mysql.

Edit /etc/my.cnf and ensure you have a line like this - set XXXX accordingly.

[mysqld]
set-variable=max_connections=XXXX

Then restart mysql
 
Thanks for your reply but i know how to "solve" (work around) it.
But i dont think thats the way how to solve the problem. The MAX in the config is set with a reason offcourse :)
 
Personally never had a shared server where the "max" is enough :)

But i guess it depends how many people you have active on the server.

(wonder why they decided to add a max_connections variable to mysql if it wasnt too be used) :)
 
As far as i can see the program is connecting to the SQL server and after that another session (socket) will be opened without closing the old.. thats the problem and that they should fix :)

Did anyone already submit something regarding this?
 
Back
Top