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

Resolved How to increase pm.max_children globally?

Bitpalast

Plesk addicted!
Plesk Guru
Seeking a way to increase the PHP FPM pm.max_children setting globally. The default value is too low for almost every domain and we want to raise it to a much higher value for all customers.

FAQ article
https://support.plesk.com/hc/en-us/articles/214528405-Server-reached-max-children-setting-5-
only describes how to do it for a single domain. I did not find a "template" php.ini file or something on a global scale to change, so that a new default pm.max_children setting is applied to all at once.
 
Default pm.max_children value is hardcoded in phpininmng. Therefore you can increase it only per-domain as it is described in the article.
 
"Tested the solution from
https://support.plesk.com/hc/en-us/articles/214528405-Server-reached-max-children-setting-5-
Then checked the result in
/opt/plesk/php/7.0/etc/php-fpm.d/DOMAIN.TLD.conf
after /usr/local/psa/bin/php_settings -u had finished.
It does not work :-( , the pm.max_children setting has not been applied to the PHP-FPM config file of the domain."

Correction: Sorry, it worked. In that file in the upper portion, the default setting is mentioned, then on the bottom line of the file, the individual setting has been inserted. Not sure why it is done that way, because it could lead to PHP reading the first value and applying that default, not continuing to read the last instance of the same value. But obviously it does work in this case.
 
Back
Top