
我的伺服器運行 10 個網站,流量非常低。配置:
- Ubuntu 20.04.5 LTS
- Nginx 1.18.0 (Ubuntu)
- PHP 7.4.3
在nginx.conf這是添加的:
upstream local_php {
server unix:/run/php/php7.4-fpm.sock;
}
在網站啟用設定檔的位置包括:
location ~ \.php$ {
include fastcgi.conf;
fastcgi_intercept_errors on;
fastcgi_pass local_php;
fastcgi_buffers 16 16k;
fastcgi_buffer_size 32k;
}
我的/etc/php/7.4/fpm/pool.d/www.conf有:
pm = ondemand
pm.max_children = 15
pm.max_requests = 10
現在發生的情況是,我的網站運作良好,但 php 日誌檔案顯示活躍子層級的數量正在穩定增加。大約一天后,它達到 15,然後 PHP 停止工作。查看進程列表,各個「年齡層」的孩子似乎都沒有目標地生活著。 PHP 日誌檔案中沒有警告,只有這項警告,當max_children
到達時:
WARNING: pid 75057, fpm_pctl_on_socket_accept(), line 518: [pool www] server reached max_children setting (15), consider raising it
我一直在嘗試調整 PHP 設定。使用pm = dynamic
,可以更快達到 max_children 。max_requests
起初較高,但降低它並沒有顯著差異。我有足夠的資源來增加max_children
一點,但這只是推遲問題,而不是解決問題。
請注意,我的伺服器沒有負載問題。記憶體使用率從未超過35%,CPU 穩定在5%。
我一定做錯了什麼,因為我認為孩子們應該在某個時候被殺死,不是嗎?PHP 日誌顯示子程序被殺死,但這總是減少空閒子程序的數量,甚至減少活躍子程序的數量:
DEBUG: pid 232350, fpm_pctl_perform_idle_server_maintenance(), line 365: [pool www] currently 8 active children, 2 spare children
DEBUG: pid 232350, fpm_got_signal(), line 82: received SIGCHLD
DEBUG: pid 232350, fpm_event_loop(), line 435: event module triggered 1 events
DEBUG: pid 232350, fpm_children_bury(), line 261: [pool www] child 289966 has been killed by the process management after 12.069386 seconds from start
DEBUG: pid 232350, fpm_pctl_perform_idle_server_maintenance(), line 365: [pool www] currently 8 active children, 1 spare children
DEBUG: pid 232350, fpm_got_signal(), line 82: received SIGCHLD
DEBUG: pid 232350, fpm_event_loop(), line 435: event module triggered 1 events
DEBUG: pid 232350, fpm_children_bury(), line 261: [pool www] child 289969 has been killed by the process management after 12.665847 seconds from start
DEBUG: pid 232350, fpm_pctl_perform_idle_server_maintenance(), line 365: [pool www] currently 8 active children, 0 spare children
子級最多 15 個的典型進程列表:
1390 vps@vps9029:/etc/php/7.4/fpm/pool.d $ ps -elf|grep php
4 S root 15528 15439 0 80 0 - 2397 - Dec20 pts/1 00:00:00 sudo tail -f php7.4-fpm.log
4 S root 15537 15528 0 80 0 - 1378 - Dec20 pts/1 00:00:12 tail -f php7.4-fpm.log
4 S root 75057 1 0 80 0 - 59077 - Dec21 ? 00:00:26 php-fpm: master process (/etc/php/7.4/fpm/php-fpm.conf)
5 S www-data 94817 75057 0 80 0 - 84357 - Dec21 ? 00:00:00 php-fpm: pool www
5 S www-data 104885 75057 0 80 0 - 84302 - Dec21 ? 00:00:00 php-fpm: pool www
5 S www-data 125566 75057 0 80 0 - 66282 - Dec21 ? 00:00:01 php-fpm: pool www
5 S www-data 143879 75057 0 80 0 - 65617 - 02:47 ? 00:00:00 php-fpm: pool www
5 S www-data 149198 75057 0 80 0 - 84441 - 03:56 ? 00:00:00 php-fpm: pool www
5 S www-data 149632 75057 0 80 0 - 84582 - 04:02 ? 00:00:08 php-fpm: pool www
5 S www-data 152959 75057 0 80 0 - 84515 - 04:43 ? 00:00:01 php-fpm: pool www
5 S www-data 178687 75057 0 80 0 - 65673 - 09:53 ? 00:00:00 php-fpm: pool www
5 S www-data 182987 75057 0 80 0 - 84178 - 10:46 ? 00:00:00 php-fpm: pool www
5 S www-data 187712 75057 0 80 0 - 84178 - 11:44 ? 00:00:00 php-fpm: pool www
5 S www-data 187713 75057 0 80 0 - 84178 - 11:44 ? 00:00:00 php-fpm: pool www
5 S www-data 197529 75057 0 80 0 - 84386 - 13:59 ? 00:00:00 php-fpm: pool www
5 S www-data 210404 75057 0 80 0 - 65569 - 16:48 ? 00:00:00 php-fpm: pool www
5 S www-data 213858 75057 0 80 0 - 65633 - 17:29 ? 00:00:00 php-fpm: pool www
5 S www-data 214975 75057 0 80 0 - 85465 - 17:44 ? 00:00:00 php-fpm: pool www
答案1
原因是來自已安裝網站之一的請求緩慢。
有相當多的 FPM/NGINX 設定可以控制子進程的活動。這些是我現在的設置,它們似乎讓孩子們得到了控制:
在/etc/php/7.4/fpm/pool.d/www.conf
:
pm = ondemand
pm.max_requests = 10
pm.max_children = 15
pm.process_idle_timeout = 10s
request_terminate_timeout = 60s
- request_terminate_timeout_track_finished = 是
在/etc/php/7.4/fpm/php.ini
:
max_execution_time = 30
default_socket_timeout = 60
在/etc/nginx/nginx.conf
:
keepalive_timeout 55;
fastcgi_read_timeout 60;