Welcome! Log In Create A New Profile

Advanced

Re: Upstream Read Timeout Upon Backend Server Offline

May 06, 2013 12:12PM
Hi Mex,

We shut them down one-by-one, 45 minutes apart. The issue only seems to occur when the first server listed is blocked however. We don't see the read timeouts if I leave the iptables rules enabled on the second server. I think that may be a false symptom related to ip_hash binding clients to the first server.

Here are the iptables rules:

Drop rule: iptables -I INPUT -s 192.168.1.0/24 -j DROP
Allow rule: iptables -D INPUT -s 192.168.1.0/24 -j DROP

I also thought about trying to add "down" to the servers in the upstream block, but as you said that would be rather complex to script.

The only error I see is a 499 error in the Nginx logs, followed by a 200:

ip.address - - [06/May/2013:01:50:53 -0400] "GET /home HTTP/1.1" 499 0 "-" "Mozilla 4.0"
ip.address - - [06/May/2013:01:52:04 -0400] "GET /home HTTP/1.1" 200 24781 "-" "Mozilla/5.0 (compatible; PRTG Network Monitor (www.paessler.com); Windows)"
SubjectAuthorPosted

Upstream Read Timeout Upon Backend Server Offline

mevans336May 06, 2013 09:46AM

Re: Upstream Read Timeout Upon Backend Server Offline

mexMay 06, 2013 09:59AM

Re: Upstream Read Timeout Upon Backend Server Offline

mexMay 06, 2013 10:01AM

Re: Upstream Read Timeout Upon Backend Server Offline

mevans336May 06, 2013 12:12PM

Re: Upstream Read Timeout Upon Backend Server Offline

mevans336May 06, 2013 12:15PM

Re: Upstream Read Timeout Upon Backend Server Offline

Maxim DouninMay 06, 2013 12:38PM

Re: Upstream Read Timeout Upon Backend Server Offline

mevans336May 06, 2013 01:47PM

Re: Upstream Read Timeout Upon Backend Server Offline

mexMay 06, 2013 02:41PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 50
Record Number of Users: 7 on March 06, 2014
Record Number of Guests: 229 on August 01, 2014
Powered by nginx    Powered by FreeBSD    PHP Powered    Powered by Percona     ipv6 ready