Edit report at https://bugs.php.net/bug.php?id=52569&edit=1

 ID:                 52569
 Comment by:         trollofdarkness at gmail dot com
 Reported by:        mplomer at gmx dot de
 Summary:            Implement "ondemand" process-manager (to allow zero
                     children)
 Status:             Analyzed
 Type:               Feature/Change Request
 Package:            FPM related
 PHP Version:        5.3.3
 Assigned To:        fat
 Block user comment: N
 Private report:     N

 New Comment:

Hello,

Ok so it is normal.

I think it would be great to make a short sum up of what's been introduced in 
the FPM configuration by this patch, and what behaviour of what already 
existing config directive has been modified. I read the entire bug file, but 
did not completely understand what's been modified / introduced about the 
config directives.

To answer your question I am running Debian Lenny 64bits. PHP has been compiled 
successfully from the last SVN sources (5.3 branch). And as I said, I used both 
Apache2 and Nginx, I tried with both sockets and host:ip methods and is has 
exactly the same behaviour with the two methods :

When FPM starts, no process is launched for the given pool (ok, that's right)
When a request comes... the web server handles it, passes it to FPM ... But 
after, I don't know, I did not see anything shocking in the log file... And 
absolutly no process is started by FPM. So the request waits until the 
webserver finally decides that FPM is not responding correctly and displays an 
error message instead (after at least 1 minute, so that's not about FPM being 
slow or something like that).


Thanks in advance.

Troll


Previous Comments:
------------------------------------------------------------------------
[2011-07-10 11:02:38] f...@php.net

pm.min_delay_between_fork has been removed since the version 9 of the patch. 
This 
is normal :)

which OS/version are you using ?

------------------------------------------------------------------------
[2011-07-09 11:47:29] trollofdarkness at gmail dot com

I think I get the same problem as dbetz .

I am using sockets (one per website) with both Apache2 and Nginx. Neither with 
the first nor the second it worked.

I tried with the use of ip:port instead of sockets but it is exactly the 
same... 

I've no idea where it comes from.

------------------------------------------------------------------------
[2011-07-09 11:08:15] trollofdarkness at gmail dot com

Hello everyone,

I tried patching the last 5.3 SVN branch with the patch. All went well (config, 
compile, etc. ...). But after restarting php-fpm I get that : 

Starting php-fpm [09-Jul-2011 16:57:37] ERROR: [/usr/local/etc/php-fpm.conf:27] 
unknown entry 'pm.min_delay_between_fork' 


Which is pretty strange because the other options are not showing any error :

This works :
[mypool]
pm = ondemand
pm.process_idle_timeout = 10
# plus the other config lines...

But this, will show the previous error message :

[mypool]
pm = ondemand
pm.process_idle_timeout = 10
pm.min_delay_between_fork = 10000 # this to avoid the known bug
# plus the other config lines...

Any idea ?

Else, beside that, if I use the pm = ondemand , there is absolutly no process 
forked. Neither at the beginning, nor after, when a request comes... 
However, pm=dynamic & pm=static still works well... ??

------------------------------------------------------------------------
[2011-07-09 08:33:10] f...@php.net

Here is a new release of the patch which is supposed to correct the double fork 
bug.

I've moved pm.min_delay_between_fork to the event layer and it's now defined in 
the global section as events.delay (default 500µs)

------------------------------------------------------------------------
[2011-07-09 08:30:31] f...@php.net

The following patch has been added/updated:

Patch Name: fpm-ondemand.v9-5.3.patch
Revision:   1310214631
URL:        
https://bugs.php.net/patch-display.php?bug=52569&patch=fpm-ondemand.v9-5.3.patch&revision=1310214631

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=52569


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=52569&edit=1

Reply via email to