Hi, On Mon, Oct 05, 2009 at 04:37:16PM -0500, Ben Fyvie wrote: > We have implemented haproxy between an nginx web server and 3 mongrel > instances. With this configuration we receive intermittent 502 errors, these > errors seem to only occur when a single mongrel instance is restarting (at > least that is how it seems). We were running haproxy version 1.3.15.5 until > I came across the following: > > http://www.mail-archive.com/[email protected]/msg00864.html > > > > So today we upgraded to 1.3.20 in hopes that our 502 problems would be > resolved, however they continue. > > > > Some interesting tidbits: > > 1. without haproxy we don't receive any 502 errors > 2. prior to the upgrade to 1.3.20 we had one request to create a new > record. That request returned a 502 to the end-user, but the record was > actually created (this means the mongrels are processing the requests) > > > > Are there steps we can take (such as specific logging options) to pinpoint > what is causing haproxy to throw the 502 errors?
Yes, first, you should absolutely check the logs. The response is there. Just grep for ' 502 ' in your logs and see the flags, they will indicate what has caused that error. Regards, Willy
