Welcome! Log In Create A New Profile

Advanced

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

Maxim Dounin
November 16, 2012 12:12PM
Hello!

On Fri, Nov 16, 2012 at 11:42:54AM -0500, pliljenberg wrote:

> The requests before (for more than 30sec) to the server X are ok, this is
> the diet request generating a 500 response (from the timeout).
> Son up til this point all looks good - which is why I don't understand why
> nginx considers the server inactive after the first fail :)

500 response?

Normally timeouts results in 504, and if you see 500 this might
indicate that in fact request failed not due to a timeout, but
e.g. due too loop detected. This in turn might mean that there
were more than one request to the server X which failed.

Try looking into error_log to see what's going on.

--
Maxim Dounin
http://nginx.com/support.html

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

Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenberg November 16, 2012 09:15AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

Maxim Dounin November 16, 2012 10:32AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenberg November 16, 2012 10:54AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

Maxim Dounin November 16, 2012 11:34AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenberg November 16, 2012 11:42AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

Maxim Dounin November 16, 2012 12:12PM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenberg November 16, 2012 01:51PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 269
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready