Starting php-fpm: [07-Jul-2014 17:52:33] WARNING: [pool app-execute]
listen.backlog(0) was too low for the ondemand process manager. I updated it
for you to 128
Well that is unfortunate, not sure why using on-demand required a backlog of
128. Essentially this php-fpm pool runs jobs then the worker
Hello!
On Sun, Jul 06, 2014 at 10:14:42PM -0400, justink101 wrote:
> Maxim,
>
> If I set the php-fpm pool listen.backlog to 0, will this accomplish what I
> want. I.e. fill up workers, once all the workers are used, fail requests.
Note that such a low value will have a downside of not toleratin
Maxim,
If I set the php-fpm pool listen.backlog to 0, will this accomplish what I
want. I.e. fill up workers, once all the workers are used, fail requests.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251476,251488#msg-251488
___
nginx mai
The only way around this would be some kind of counter keeping track of
whats available and if max is reached create a file where you test on in a
nginx config, maybe Lua can do this counting part.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251476,251478#msg-251478
Hello!
On Sat, Jul 05, 2014 at 10:47:43PM -0400, justink101 wrote:
> I have a php-fpm pool of workers which is 6. There are long running requests
> being sent, so I have the following fastcgi directives set:
>
> fastcgi_connect_timeout 15;
> fastcgi_send_timeout 1200;
> fastcgi_read_timeout 1200
I have a php-fpm pool of workers which is 6. There are long running requests
being sent, so I have the following fastcgi directives set:
fastcgi_connect_timeout 15;
fastcgi_send_timeout 1200;
fastcgi_read_timeout 1200;
However right now, if the php-fpm pool of workers is full, a request waits
the
