Re: Nginx upstream servers status

[Sajan Parikh]

In your proxy_next_upstream, why do you have 'off' enabled. off — it forbids the request transfer to the next server. Remove 'off' from that line. Sajan Parikh Owner, Noppix LLC e: sa...@noppix.com p: (563) 726-0371 On 07/03/2013 12:37 AM, Sandeep L wrote: @Parikh I tried with  proxy_next_upstream also but facing same issue. Regarding fail_timeout I used values from 10s to 30s but facing same issue. I used following configuration, just check and let me know If I am missing any thing. upstream appcluster {   server host1.example.com:8080 max_fails=2 fail_timeout=10s;   server host2.example.com:8080 max_fails=2 fail_timeout=10s; } server {                          listen *;                 location / {                         proxy_pass  http://appcluster;                         proxy_next_upstream error timeout http_404 http_500 http_502 http_503 http_504 off;                         proxy_set_header  X-Real-IP  $remote_addr;                 } } Thanks, Sandeep. > To: nginx@nginx.org > Subject: Re: Nginx upstream servers status > From: nginx-fo...@nginx.us > Date: Wed, 3 Jul 2013 01:11:20 -0400 > > you allow 600 seconds to pass until you npotice, that your upstream-server > is not responsible. > > ... max_fails=2 fail_timeout=300s; > > why? > > Posted at Nginx Forum: http://forum.nginx.org/read.php?2,240513,240515#msg-240515 > > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx