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

Forwarded to devs Add-on overwrite pm.max_children settings

B4c4rd1

Regular Pleskian
TITLE:
Addon overwrite pm.max_children settings
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx Version 17.8.11 Update #74
Ubuntu 16/18
PROBLEM DESCRIPTION:
If a service plan is created and this plan has the setting: pm.max_children 125, this value is overwritten by every other add-on.

In this case, no setting must be activated in the add-on.​
STEPS TO REPRODUCE:
For example: The service plan has the settings: pm.max_children 125. The add-on is only intended to increase the storage space. After activation the add-on, the PHP setting: pm.max_children is reset to the value 5.​
ACTUAL RESULT:
Reset the value to 5​
EXPECTED RESULT:
If the settings: pm.max_children is not set (in the add-on), the addon may not overwrite the default setting (125) or individual settings​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Last edited:
The setting also overwrites changes previously made. Change the setting to 125 and then activate an add-on. The setting will then be reset ...
 
Thank you for the report. The bug was confirmed and submitted as PPP-46475
 
Back
Top