hi willy,
thanks for your efforts on this. i do see. i haven't been using
frontends at all in haproxy.cfg but i can see the benefit of doing
what you describe. mongrel though isn't the static fileserver of
choice however. currently i do a bunch of rewrites in my nginx conf to
split out the static
On Sat, Oct 10, 2009 at 04:10:26AM -0400, Greg Gard wrote:
hi willy,
thanks for your efforts on this. i do see. i haven't been using
frontends at all in haproxy.cfg but i can see the benefit of doing
what you describe. mongrel though isn't the static fileserver of
choice however. currently
Hi Greg,
On Thu, Oct 08, 2009 at 09:56:37PM -0400, Greg Gard wrote:
hi all,
i have been watching this thread with some interest and had a comment
about mongrel and health checks. i have found that i can have mongrel
serve up a static file as a health check that uses a separate thread
from
@formilux.org
Subject: Re: 502 errors continue
On Wed, Oct 07, 2009 at 05:21:00PM -0500, Ben Fyvie wrote:
Thanks Willy,
it's clear that the server unexpectedly closed the connection or died
You are absolutely correct. We've found that the problem is not to do with
malformed headers, so we don't
that it turned out to be a problem with mongrel and not
haproxy.
Ben Fyvie
-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Wednesday, October 07, 2009 11:53 PM
To: Ben Fyvie
Cc: haproxy@formilux.org
Subject: Re: 502 errors continue
On Wed, Oct 07, 2009 at 05:21:00PM
Hi Ben,
On Thu, Oct 08, 2009 at 05:42:34PM -0500, Ben Fyvie wrote:
(...)
Glad that most of your main issues are getting solved !
Thanks again for everyone's input. I posted my questions to the mongrel
mailing list earlier this week and have not received any input from them.
I'm glad the
, however prior to haproxy, the mongrel
instance seemed to respond just fine to nginx prior to restarting.
Ben Fyvie
-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Tuesday, October 06, 2009 6:11 PM
To: Ben Fyvie
Cc: haproxy@formilux.org
Subject: Re: 502 errors continue
On Wed, Oct 07, 2009 at 09:50:13AM -0500, Ben Fyvie wrote:
Thanks Willy,
I came to a similar conclusion after breaking apart the error line in the
log using your documentation. I updated the pastie with the breakout:
http://pastie.org/private/nfvbtq236x8jp9ynj4dg
You did a nice job here. I
with the server
(mongrel in our case)???
Ben Fyvie
-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Wednesday, October 07, 2009 4:23 PM
To: Ben Fyvie
Cc: haproxy@formilux.org
Subject: Re: 502 errors continue
On Wed, Oct 07, 2009 at 09:50:13AM -0500, Ben Fyvie wrote:
Thanks
On 10/7/09 3:21 PM, Ben Fyvie wrote:
So what our problem really comes down to is why doesn't mongrel quietly stop
receiving requests after monit issues the initial kill. (FYI - it is our
understanding that calling mongrel stop also issues a kill command so
there is no nicer way to ask it to shut
On Wed, Oct 07, 2009 at 05:21:00PM -0500, Ben Fyvie wrote:
Thanks Willy,
it's clear that the server unexpectedly closed the connection or died
You are absolutely correct. We've found that the problem is not to do with
malformed headers, so we don't need to debug that like I had previously
: 502 errors continue
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
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
13 matches
Mail list logo
