RE: reducing check requests with same servers in many backends

I don't know of a way to only define the server list once, but in subsequent backends you can use 'track backend_name/sv_name' instead of 'check' to reduce the health check spam. One gotcha I ran into is that if I have 'option httpchk HEAD /my/health/url' in the backend with 'check's I also

RE: Slowness in establishing connections from ruby to Haproxy after upgrading from 1.4.8 to 1.4.18

Is there an ETA for this fix making its way to a 1.4 release? Also, is it known what version introduced undesirable behavior with ruby clients? 1.4.9 to 1.4.18 is a fairly loose bound... Thanks, Bryan -Original Message- From: Willy Tarreau [mailto:w...@1wt.eu] Sent: Saturday, December

RE: Apache translates 500 to 502 from haproxy

Hello, Check that Cherrypy is serving up valid HTTP. You could also try setting HAProxy to balance in TCP mode instead of HTTP mode, though if this helps it would just be masking any problem that might exist. I once had a backend 500 response translated to 502 by HAProxy balancing in HTTP

maxconn vs. option httpchk

Hi all, I've noticed an odd (lack of) interaction between maxconn and option httpchk... If a server's maxconn limit has been reached, it appears that HTTP health checks are still dispatched. If I've configured the maxconn limit to match the number of requests the backend server can