{"id":5389,"date":"2017-03-04T15:01:06","date_gmt":"2017-03-04T20:01:06","guid":{"rendered":"https:\/\/www.tecklyfe.com\/?p=5389"},"modified":"2017-03-04T15:01:06","modified_gmt":"2017-03-04T20:01:06","slug":"adjusting-child-processes-php-fpm-nginx-fix-server-reached-pm-max_children-setting","status":"publish","type":"post","link":"https:\/\/www.tecklyfe.com\/adjusting-child-processes-php-fpm-nginx-fix-server-reached-pm-max_children-setting\/","title":{"rendered":"Adjusting Child Processes For PHP-FPM Nginx – Fix Server Reached pm.max_children Setting"},"content":{"rendered":"

\"\"As an addition to my previous NGINX articles<\/a>, today we’ll discuss how to adjust the number of child processes for PHP-FPM to fix the common error of “server reached pm.max_children” in the logs. This is a follow-up to the LEMP Install NGINX PHP7 MySQL on Ubuntu 16.04 Server<\/a> or LEMP Install NGINX PHP7 MySQL on CentOS 7 \/ RHEL \/ Fedora<\/a> articles. By default, the pm.max_children is set to 5 when using PHP-FPM.<\/p>\n

Reasons Why You Reach max_children<\/h2>\n

The most common reasons why your PHP-FPM would reach the max_children are:<\/p>\n