On 12 September 2012 16:43, Brian Shore <[email protected]> wrote: > Hi, > Is it possible to configure a backend with multiple http-check URLs > and require all of them to succeed instead of requiring any to > succeed?
I'm not aware of a non-hacky way to do it (chained HAProxy instances, etc). I may well be wrong, though ... > In my testing last night using 1.4.17, haproxy happily > checked both URLs but only marked the server as down when both checks > failed. I wasn't aware it did that - nice to know! Willy - are multiple checks by design or by accident? :-) > The test configuration backend looks like this: > > listen test *:80 > stats auth admin:admin > option httpchk HEAD /head.txt > option httpchk GET /maint > http-check disable-on-404 > server localhost 127.0.0.1:8001 check port 8001 inter > 5s downinter 5s > > > The idea is to always use "HEAD /head.txt" check failures to > indicate a down server, and to only use "GET /maint" 404 responses to > initiate soft-stop maintenance mode. Would http://cbonte.github.com/haproxy-dconv/configuration-1.4.html#http-check%20disable-on-404 help? It allow for the nicer (IMHO) behaviour of variable rise/fall settings for the healthcheck, but an immediate drop out on (and *only* on) 404s. Jonathan -- Jonathan Matthews Oxford, London, UK http://www.jpluscplusm.com/contact.html
