• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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