up vote 0 down vote favorite
1
share [g+] share [fb]

I'm using Amazon's elastic load balancing across several machines that are running nginx. The problem is, after running for fifteen minutes or so, ELB starts to mark all of the machines as dead. When we look at the nginx access logs, however, the ELB requests are returning 200's in less than 1 ms (we just have nginx serving the a static file for the ELB healthcheck). So, I'm not sure how to figure out what's going on.

Is there either some way we can get a more detailed description of why ELB thought all of the machines were bad, or any general tips for situations that might cause this? I'm really stumped trying to figure out what I can try next, to debug.

link|improve this question
Do you have Amazon Support? – Tom O'Connor Jan 24 at 0:37
Less than 1ms sounds like localhost retrieval, have you confirmed the file is accessible from other networks? – thinice Jan 24 at 0:42
Amazon Support is a good idea. We don't have it but probably we would shell out for it. ELB isn't accessing the file, it's accessing HTTP:80/the_file_name which nginx serves in < 1 ms. – lacker Jan 24 at 1:09
A good (if somewhat dated) diagnostic procedure for ELBs can be found here - and a series of automated tests here. Perhaps they will provide some additional information for you (that you can include in your question, if it doesn't reveal the problem for you). – cyberx86 Jan 24 at 1:58
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.