On Wed, Sep 12, 2012 at 9:24 AM, Jonathan Matthews <[email protected]> wrote: > I'm not aware of a non-hacky way to do it (chained HAProxy instances, > etc). I may well be wrong, though ...
I would even be interested in those at least to consider the options. I haven't come up with a way to do it even with chained instances. >> 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. As in the included backend configuration, this option is enabled. I initially thought there would be confusion if the "HEAD /head.txt" status check returned a 404. But we can probably just tweak the app server so that a 404 can't result for this specific path. Thanks for your reply. -- Brian Shore Senior Software Engineer, Security Architect Network Redux, LLC 5200 SW Macadam Ave Ste 450 Portland, Oregon 97239 Desk: 503-274-9905 x503
