Applicable to:
- Plesk for Linux
Symptoms
-
PHP handler FPM application server by Apache or FPM application server by nginx is selected in website PHP Settings.
-
The following message can be found in PHP-FPM error log (
/var/log/phpX-fpm.logor/var/log/plesk-phpXX-fpm/error.log, where X is a PHP version):CONFIG_TEXT: WARNING: [pool example.com] server reached max_children setting (5), consider raising it
ERROR: unable to read what child say: Bad file descriptor (9)OR
CONFIG_TEXT: [pool example.com] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 4 idle, and 152 total children
-
The website is not accessible with:
CONFIG_TEXT: 503 Service Temporarily Unavailable
or:
CONFIG_TEXT: 502 Bad Gateway
or:
CONFIG_TEXT: 500 Internal Server Error
-
Server performance may be poor.
Cause
The limit of pm.max_children (PHP-FPM pool parameter) for website example.com has been reached.
Additionally, pm.start_servers, pm.min_spare_servers and pm.max_spare_servers might need adjusting.
Resolution
Starting from Plesk Onyx 17.5.30 Update #32, the PHP-FPM limits can be changed via Plesk UI as below:
- Log into Plesk
- Browse to Domains > example.com > PHP Settings > PHP-FPM Settings
- Adjust the PHP-FPM settings for the domain
It is possible to set PHP-FPM Settings for multiple domains via Service Plan. Check the following article for the details.
For Plesk versions below than Plesk Onyx, the following solution can be used:
-
Connect to the server using SSH
-
Create the file
php.iniin directory/var/www/vhosts/system/example.com/conf/:# touch /var/www/vhosts/system/example.com/conf/php.ini
-
Open the file
php.iniin a text editor and add the following records:[php-fpm-pool-settings]pm.max_children = 40 -
Browse to Domains > example.com > PHP Settings and click OK button to update PHP-FPM pool configuration file
If the issue persists, increase the value of pm.max_children to a greater value.
Note: In some cases, not optimized application code can cause long living PHP-FPM processes, which is causing limit overuse. In such cases the best practice is to resolve the application code issue instead of raising pm.max_children limit.
Additional Information:
When it is required to check if there are any other domains affected by exceeded limits, use the following command line to parse PHP-FPM error logs:
# grep "server reached max_children setting" /var/log/*php*-fpm/error.log | awk '{print $5}' | sort -n | uniq -c
Comments
8 comments
Great help and tutorial ! Thanks a lot
Possible to apply this setting to all domains with single file editing? I have lots of domains to be configured 1 by 1
@Sharul Hafiz You can check the article mentioned in Additional Information section - https://support.plesk.com/hc/en-us/articles/115001201949
Keep in mind that increasing of pm.max_children parameter for all domains can affect the server performance significantly. It is better to filter only affected domains in /var/log/plesk-phpXX-fpm/error.log file
===
grep "server reached max_children setting" /var/log/plesk-phpXX-fpm/error.log
===
and adjust max_children just for them.
@Nikolay What is the limit of pm.max_children? let say if I have 10GB free ram.
@Sharul
The setting is purely depends on amount of traffic for the website. Try to double the default value (from 5 to 10) and monitor the site for several days.
If the same error appears again, analyze the time period between reaching MaxChildren. In case the time like several minutes, double the value again (from 10 to 20), in case the error appears once a day, just add one more child to the configured value (20 to 21).
Typically, 20 is more than enough for medium-loaded websites.
This line
# grep "server reached max_children setting" /var/log/php-fpm/error.log | awk '{print $5}' | sort -n | uniq -cis wrong, as it should be
# grep "server reached max_children setting" /var/log/plesk-phpXX-fpm/error.log | awk '{print $5}' | sort -n | uniq -cMay you insert
in Additional PHP directives field of PHP Settings page for domain?
Hello Marco,
Both files (/var/log/php-fpm/error.log and /var/log/plesk-phpXX-fpm/error.log) exist on the filesystem. The first is used to store errors from system php-fpm, and the second is used when we are speaking about php-fpm which is provided bu Plesk.
Meanwhile, I have edited the article in this way:
# grep "server reached max_children setting" /var/log/*php*-fpm/error.log | awk '{print $5}' | sort -n | uniq -c
As for the second question, Additional PHP directives field is used to insert configuration directives in /var/www/vhosts/system/example.com/conf/php.ini file (configuration file for php itself), however pm.max_children directive should be added to the configuration file of php-fpm pool (/var/www/vhosts/system/example.com/conf/php.ini).
So, this is two different files. And now Plesk could manage only php settings, but not php fpm pool settings.
If you would like Plesk to manage php fpm pool settings, vote for this feature on Plesk Uservoice portal.
Please sign in to leave a comment.