On Thursday 22 May 2014 22:14:23 Lyle wrote:
> On 22/05/2014 19:32, Valentin V. Bartenev wrote:
> > On Thursday 22 May 2014 16:26:54 Phil Knight wrote:
> >> Hi
> >>
> >> We are having an issue passing data to CGI scripts via PATH_INFO
> >> environment variable.
> >>
> >> for example:-
> >>
> >> htt
On 22/05/2014 19:32, Valentin V. Bartenev wrote:
On Thursday 22 May 2014 16:26:54 Phil Knight wrote:
Hi
We are having an issue passing data to CGI scripts via PATH_INFO
environment variable.
for example:-
http://domain.com/cgi-bin/script.cgi/=
On various apache servers this works fine and t
Did you ever get a response to this...We are seeing the following:
no live upstreams while connecting to upstream
we know the upstream servers are not crashing but are trying to determine
how/why they are being deemed as down. The nginx gives no information on
this and the servers show no er
On Thursday 22 May 2014 16:26:54 Phil Knight wrote:
> Hi
>
> We are having an issue passing data to CGI scripts via PATH_INFO
> environment variable.
>
> for example:-
>
> http://domain.com/cgi-bin/script.cgi/=
>
> On various apache servers this works fine and the PATH_INFO variable
> will con
Hi
We are having an issue passing data to CGI scripts via PATH_INFO
environment variable.
for example:-
http://domain.com/cgi-bin/script.cgi/=
On various apache servers this works fine and the PATH_INFO variable
will contain "/=", on our nginx server we are getting a 403 forbidden
error.
Thanks, my math is not wrong my concept about php-fpm was wrong. I was
thinking each child can handle 4 requests/sec. :(
On Thu, May 22, 2014 at 7:52 PM, Reinis Rozitis wrote:
> pm.max_children = 250
>> pm.start_servers = 40
>> pm.max_requests = 4
>>
>
> Any clue why requests are still
pm.max_children = 250
pm.start_servers = 40
pm.max_requests = 4
Any clue why requests are still getting into php-fpm queue and max
children also reached errors occuring, even max_children are 250 * 4.
??
Your math is wrong - there is no such 250 * 4, because pm.max_requests
is
You think, issue is not related to nginx but nginx and php-fpm work
together, that is the reason i posted the question on nginx forums.
On Thu, May 22, 2014 at 7:34 PM, shahzaib shahzaib wrote:
> Met you after a long time maxim :) how's everything ?
>
>
> On Thu, May 22, 2014 at 5:09 PM, Maxim
Met you after a long time maxim :) how's everything ?
On Thu, May 22, 2014 at 5:09 PM, Maxim Dounin wrote:
> Hello!
>
> On Thu, May 22, 2014 at 04:03:37PM +0500, shahzaib shahzaib wrote:
>
> > Anyone ?
>
> [...]
>
> > > On Thu, May 22, 2014 at 1:27 PM, Lord Nynex
> wrote:
> > >
> > >> This doe
>No, I didnot find a way to resolve this, I have to make the cached files to
a smaller count and add more devices to share the load ...
But is this split with samller devices "solve" the problem? I mean how many
file could you have in cache? How many devices you have?
Posted at Nginx Forum:
http
Hello!
On Thu, May 22, 2014 at 04:03:37PM +0500, shahzaib shahzaib wrote:
> Anyone ?
[...]
> > On Thu, May 22, 2014 at 1:27 PM, Lord Nynex wrote:
> >
> >> This does not seem like an nginx issue?
--
Maxim Dounin
http://nginx.org/
___
nginx mailing
On Thu, May 22, 2014 at 5:05 PM, ixos wrote:
> > Can I know what is the ingest Gbps into the SSDs when you hit the
> problem?
> About ~500 Mbps
>
> > and How many cached file nodes in cache-manager? I have millions ...
> Between 7-9 milions
>
> Can you tell more about your configuration os/nginx/
Anyone ?
On Thu, May 22, 2014 at 1:31 PM, shahzaib shahzaib wrote:
> Following is the nginx config :
>
> user nginx;
> # no need for more workers in the proxy mode
> worker_processes 16;
> error_log /var/log/nginx/error.log crit;
> worker_rlimit_nofile 409600;
> events {
> worker_connections
> Can I know what is the ingest Gbps into the SSDs when you hit the
problem?
About ~500 Mbps
> and How many cached file nodes in cache-manager? I have millions ...
Between 7-9 milions
Can you tell more about your configuration os/nginx/cache? And how have you
tried to solve the problem.
Posted a
Following is the nginx config :
user nginx;
# no need for more workers in the proxy mode
worker_processes 16;
error_log /var/log/nginx/error.log crit;
worker_rlimit_nofile 409600;
events {
worker_connections 10240; # increase for busier servers
use epoll; # you should use epoll here for Linux
This does not seem like an nginx issue?
On Thu, May 22, 2014 at 1:24 AM, shahzaib shahzaib wrote:
> These are the new status for php-fpm now :
>
> pool: stats
> process manager: dynamic
> start time: 22/May/2014:12:17:39 +0500
> start since: 3975
> accepte
These are the new status for php-fpm now :
pool: stats
process manager: dynamic
start time: 22/May/2014:12:17:39 +0500
start since: 3975
accepted conn:866645
listen queue: 0
max listen queue: 2163
listen queue len: 65535
idle processe
Hello,
We're using nginx + php-fpm. Please check the following configurations
in php-fpm and sysctl in order to handle large amount of php-fpm request,
but still 1000+ requests are getting into queue every 15min.
php-fpm.d/stats.conf
[stats]
listen = 127.0.0.1:9000
user = apache
group = apa
18 matches
Mail list logo
