php-fmp时不时有502的报错,查到php-fpm.log有WARNING,如下:
[17-Jan-2017 14:38:06] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 170 idle, and 237 total children
[17-Jan-2017 14:38:07] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 177 idle, and 245 total children
php-fpm.conf的配置:
[www]
listen = /tmp/php-cgi.sock
listen.backlog = -1
listen.allowed_clients = 127.0.0.1
listen.owner = www
listen.group = www
listen.mode = 0666
user = www
group = www
pm = dynamic
pm.max_children = 800
pm.start_servers = 230
pm.min_spare_servers = 180
pm.max_spare_servers = 360
request_terminate_timeout = 300
request_slowlog_timeout = 300
slowlog = var/log/slow.log
rlimit_files = 51200
其中max_spare_servers不是已经大于上面WARNING的值吗? 为什么总是会有502
pm.max_children = 800
pm.start_servers = 230
pm.min_spare_servers = 180
pm.max_spare_servers = 360
Copyright 2014-2025 https://www.php.cn/ All Rights Reserved | php.cn | 湘ICP备2023035733号
看一下net.core.somaxconn这个值,它定义了系统中每一个端口最大的监听队列的长度,这是个全局的参数,默认值为128;如果这个值过小,是会造成这种情况的,毕竟我看到你的日志中,idel的进程其实还有不少,说明不是进程不够,而是进程根本还没有起作用就已经有问题了。
你可以通过下面这个命令查看:
改动的话可以
@akay
最近又有2次seems busy的报错。
上次net.core.somaxconn这个值已经更新,如下:
php-fpm.conf的配置目前如下:
最近还是有2次seems busy的报错。
这又是怎么回事?
pm.max_children = 800
pm.start_servers = 320
pm.min_spare_servers = 180
pm.max_spare_servers = 360
这个配置 ... 太大了....