On 4/16/2018 6:43 AM, Jarno Huuskonen wrote:
There's also http-check disable-on-404
(http://cbonte.github.io/haproxy-dconv/1.5/configuration.html#4.2-http-check%20disable-on-404)
I couldn't get this to work at first. If I put the disable-on-404
option in the actual back end, it complains like this:
[WARNING] 105/095152 (5379) : config : 'disable-on-404' will be ignored
for backend 'be-cdn-9000' (requires 'option httpchk').
That makes sense, because I'm using tracking, not actual health checks
in that back end. So I moved it to the check back end, and it gave me
much worse errors:
[ALERT] 105/095234 (7186) : config : backend 'be-cdn-9000', server
'planet': unable to use chk-cdn-9000/planet fortracking: disable-on-404
option inconsistency.
[ALERT] 105/095234 (7186) : config : backend 'be-cdn-9000', server
'hollywood': unable to use chk-cdn-9000/hollywood fortracking:
disable-on-404 option inconsistency.
[ALERT] 105/095234 (7186) : Fatal errors found in configuration.
Eliminating the "track" config and doing the health checks in the actual
back end has fixed that. I need to do some testing to see whether it
does what I want it to do.
I am curious about why I couldn't use "track".
Thanks,
Shawn
