Hi Joe, On Mon, Dec 06, 2010 at 03:19:36PM -0800, Joe Williams wrote: > > 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.
I just glanced over that thread and I agree we should get this fixed one way or another. It's not really a bug but a side effect of dependencies between features. At the very least, we should document the matrix of all tracked/tracking modes with their possible options (even if we explicitly have to enable httpchk and disable-on-404 in both backends for whatever reason). Willy
