On Dec 6, 2010, at 2:45 PM, Bryan Talbot wrote: > I worked around this issue by including the "option httpchk" in the > backend but never using the "check" option for the servers in that > backend that are tracked. The server lines do contain the "track" > option. > > > backend be1 > balance roundrobin > http-check disable-on-404 > option httpchk HEAD /online.php HTTP/1.1\r\nHost:\ healthcheck > server 1.2.3.4 1.2.3.4:80 check > > backend be2 > balance roundrobin > http-check disable-on-404 > option httpchk HEAD /online.php HTTP/1.1\r\nHost:\ healthcheck > server 1.2.3.4 1.2.3.4:80 track be1/1.2.3.4
Thanks Bryan, that should hold me over for now. This seems like a bug IMHO, track should cause the backend to "inherit" http-check disable-on-404 from the main backend. -Joe > On Mon, Dec 6, 2010 at 10:51 AM, Joe Williams <[email protected]> wrote: >> Just to add some info to this thread, I did some testing and I get some >> combination of the following errors depending on where (default, backends, >> etc) I have the disable-on-404 directive. >> >> config : 'disable-on-404' will be ignored for backend 'test' (requires >> 'option httpchk'). >> config : backend 'test', server 'test': unable to use joe/node001 for >> tracing: disable-on-404 option inconsistency. >> config : 'disable-on-404' will be ignored for frontend 'http_proxy' >> (requires 'option httpchk'). >> >> I assume this is by design for some reason but certainly seems like a >> desirable feature. Can anyone point me in the right direction regarding a >> writing a patch to "fix" it? >> >> Thanks. >> -Joe >> >> >> On Dec 6, 2010, at 8:55 AM, Joe Williams wrote: >> >>> Anyone have any thoughts? Is it possible to use tracking and disable-on-404 >>> together? >>> >>> -Joe >>> >>> >>> On Dec 2, 2010, at 3:41 PM, Joe Williams wrote: >>> >>>> >>>> On Dec 2, 2010, at 2:28 PM, Krzysztof Olędzki wrote: >>>> >>>>> On 2010-12-02 21:28, Joe Williams wrote: >>>>>> >>>>>> List, >>>>>> >>>>>> I am attempting to enable the disable-on-404 option on only the >>>>>> backends that other backends track. It seems that the secondary >>>>>> backends do not like this and error out saying it is "inconsistent" >>>>>> even if disable-on-404 is only enabled in the backend that they >>>>>> track. Is it possible to have disable-on-404 without httpchk in each >>>>>> backend? >>>>> >>>>> Yes, you need to enable disable-on-404 on both tracked and tracking >>>>> backends. >>>> >>>> Doesn't that also mean that I have to enable httpchk on all those backends >>>> as well? >>>> >>>> -Joe >>>> >>>> >>>> Name: Joseph A. Williams >>>> Email: [email protected] >>>> Blog: http://www.joeandmotorboat.com/ >>>> Twitter: http://twitter.com/williamsjoe >>>> >>>> >>> >>> Name: Joseph A. Williams >>> Email: [email protected] >>> Blog: http://www.joeandmotorboat.com/ >>> Twitter: http://twitter.com/williamsjoe >>> >>> >> >> Name: Joseph A. Williams >> Email: [email protected] >> Blog: http://www.joeandmotorboat.com/ >> Twitter: http://twitter.com/williamsjoe >> >> >> Name: Joseph A. Williams Email: [email protected] Blog: http://www.joeandmotorboat.com/ Twitter: http://twitter.com/williamsjoe
