Re: Possibly bug in monitor-uri?

On 10/2/11 1:57 PM, Slawek wrote: On 02/10/2011 21:44, Cyril Bonté wrote: I've following setup: haproxy-public -> varnish -> haproxy-director, where haproxy-public monitors haproxy-director. I noticed that haproxy frequently fails to intercept URI specified in monitor-uri and passes that reques

Re: Possibly bug in monitor-uri?

On 02/10/2011 21:44, Cyril Bonté wrote: I've following setup: haproxy-public -> varnish -> haproxy-director, where haproxy-public monitors haproxy-director. I noticed that haproxy frequently fails to intercept URI specified in monitor-uri and passes that request to backend. So - in consequence

Re: Possibly bug in monitor-uri?

Hi Slawek, Le Dimanche 2 Octobre 2011 21:32:57 Slawek a écrit : > Hi all, > > I've following setup: haproxy-public -> varnish -> haproxy-director, > where haproxy-public monitors haproxy-director. > > I noticed that haproxy frequently fails to intercept URI specified in > monitor-uri and passes

Possibly bug in monitor-uri?

Hi all, I've following setup: haproxy-public -> varnish -> haproxy-director, where haproxy-public monitors haproxy-director. I noticed that haproxy frequently fails to intercept URI specified in monitor-uri and passes that request to backend. So - in consequence - haproxy is marking that back

avoiding CLOSE_WAIT on client side after client/server timeout

Hi, I noticed that both for tcp and http connections then client/server timeout is reached and haproxy tears the connection - the client side socket is CLOSE_WAIT. Is there a clean way to make haproxy tear the connection to the client. Thanks Alex

fallback of established tcp connections

Hi, There is a client which establishes a persistent tcp connection to the server, and haproxy in the middle which has a main server and backup server. Then main server goes offline , the connections are reestablished to the backup server just fine. The problem is that once main server is bac