Bug #69890 [Com]: pm.ondemand does not kill children after reaching max limit
Edit report at https://bugs.php.net/bug.php?id=69890&edit=1
ID: 69890
Comment by: lofesa at gmail dot com
Reported by: vadimyer at gmail dot com
Summary: pm.ondemand does not kill children after reaching
max limit
Status: Open
Type: Bug
Package: FPM related
Operating System: Debian 8.1 x64
PHP Version: 7.0.0alpha1
Block user comment: N
Private report: N
New Comment:
Same issue. Centos 7. php 7.0.3. Children processes are not killed. Master process are doing nothing
unless send messages to systemd like this
sendmsg(21, {msg_name(21)={sa_family=AF_LOCAL, sun_path="/run/systemd/notify"},
msg_iov(1)=[{"READY=1\nSTATUS=Processes active:"..., 84}], msg_controllen=0, msg_flags=0},
MSG_NOSIGNAL) = 84
close(21)
Previous Comments:
------------------------------------------------------------------------
[2015-08-19 05:34:50] satanistlav at mail dot ru
It seems to be only Debian 8 bug.
No such bug on Debian 7 or Ubuntu 12
------------------------------------------------------------------------
[2015-06-20 13:39:22] vadimyer at gmail dot com
Description:
------------
Looks like php7-fpm doesn't kill its children while in ondemand mode.
Test script:
---------------
Probably test "script" in this case is www.conf config:
user = www-data
group = www-data
listen = 127.0.0.1:9007
pm = ondemand
pm.max_children = 100
pm.process_idle_timeout = 10s
Expected result:
----------------
After spawning 100 children processes the system should start killing those processes if no longer
needed, depending on the pm.process_idle_timeout setting.
Actual result:
--------------
After spawning 100 children processes all children still exist and aren't going to be killed.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=69890&edit=1
Thread (8 messages)