PHP-FPM: A project site frequently appears 503 problem resolution (WARNING: [Pool www] server reached Pm.max_children setting (), consider raising it)

Service is NGINX+PHP-FPM configuration,

After running for a period of time, it will often appear:

WARNING: [Pool www] server reached Pm.max_children setting (a), consider raising it sub-process reaches the maximum number of child processes required

　　

503/502 generally because of server maintenance or overload, the recent server is not maintenance, query monitoring records found that the load is not very high, guess is not the server on some configuration of the project has a limit, view nginx,php log discovery:

Find the php-fpm.conf file to find PHP log errors

[15-nov-2017 15:23:51] WARNING: [Pool www] server reached Pm.max_children setting (5), consider raising it[15-nov-2017 17:10:53] WARNING: [Pool W WW] Server reached Pm.max_children setting (5), consider raising it[15-nov-2017 17:12:56] WARNING: [Pool www] server reach Ed Pm.max_children setting (5), consider raising it[15-nov-2017 18:29:28] WARNING: [Pool www] server reached Pm.max_childr En setting (5), consider raising it[16-nov-2017 10:25:17] WARNING: [Pool www] server reached Pm.max_children, setting (5), Consider raising it

　　

This warning occurs frequently, the maximum number of child processes, the query php-fpm configuration file www.conf, found that the Pm.max_children is the default configuration, obviously because the setting value is too small to cause

Problem solving:

Modify

Pm.start_servers =   //php-fpm Start process number pm.min_spare_servers =   minimum number of idle processes in//php-fpm pm.max_spare_servers = 24   //PHP-FPM Maximum Idle Process pm.max_requests =   //All child process restart time

　　

Reference: https://lirongyao.com/server-reached-pm-max_children-setting.html

PHP-FPM: A project site frequently appears 503 problem resolution (WARNING: [Pool www] server reached Pm.max_children setting (), consider raising it)