Hey Willy,

So we are now hit by the side effect of this fix i.e. disabling httpclose. 

Two problems:

1. Entries in the log are missing, I guess you already warned me about it.
Do you think if we disable keep alive in our Apache fronting haproxy, this
will problem will go away?
2. Related to one, but an interesting one. 
      - A request comes to haproxy, as configured after waiting in haproxy
queue for 10 seconds due to backend free connection unavailable, it sends a
503 back, logged correctly in haproxy and apache
      - The client retries, I think with Keep Alive over the same connection
and it sees a 400 status back. Now this request is no where in haproxy logs
so there is no way to see what happened in haproxy and who really dropped
the ball. The connection never made it to the backed cherrypy server since
it logs each request it receives.

Thanks
Sachin




-----Original Message-----
From: Sachin Shetty [mailto:sshe...@egnyte.com] 
Sent: Wednesday, June 15, 2011 5:23 PM
To: 'Willy Tarreau'
Cc: 'Cassidy, Bryan'; 'haproxy@formilux.org'
Subject: RE: Apache translates 500 to 502 from haproxy

tried with option http-server-close instead of option httpclose - no luck it
does not work. The only way I can get it to work is without either.

Thanks
Sachin

-----Original Message-----
From: Willy Tarreau [mailto:w...@1wt.eu] 
Sent: Wednesday, June 15, 2011 12:40 PM
To: Sachin Shetty
Cc: 'Cassidy, Bryan'; haproxy@formilux.org
Subject: Re: Apache translates 500 to 502 from haproxy

On Wed, Jun 15, 2011 at 12:11:58PM +0530, Sachin Shetty wrote:
> I also think apache is the issue. I think we have a few mischievous
modules
> like mod_rpaf that I need to disable and test. I will keep you posted. 
> 
> For now do you see any severe problem if I disabe httpclose as a
workaround?

As I said, in theory no, unless you need haproxy to analyse more than one
request per connection. But please do make a test with http-server-close.
While there is little chance that it helps, it's not completely impossible
because it is able to reinforce keep-alive on the client side even if it is
disable on the server side.

Willy


Reply via email to