Welcome! Log In Create A New Profile

Advanced

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

November 16, 2012 01:51PM
> 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.

You're correct - its a 504.
[16/Nov/2012:12:40:48 +0100] "POST /url HTTP/1.1" 403 454 Time: 300.030 Upstream-time: 300.004, 0.003 Upstream: XXX, YYY Upstream-status: 504, 403
SubjectAuthorPosted

Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenbergNovember 16, 2012 09:15AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

Maxim DouninNovember 16, 2012 10:32AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenbergNovember 16, 2012 10:54AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

Maxim DouninNovember 16, 2012 11:34AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenbergNovember 16, 2012 11:42AM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

Maxim DouninNovember 16, 2012 12:12PM

Re: Upstream max_fails, fail_timeout and proxy_read_timeout

pliljenbergNovember 16, 2012 01:51PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 85
Record Number of Users: 7 on March 06, 2014
Record Number of Guests: 184 on July 08, 2014
Powered by nginx    Powered by FreeBSD    PHP Powered    Powered by Percona     ipv6 ready