On Thu, Oct 02, 2014 at 11:29:27AM +0200, Willy Tarreau wrote: > On Fri, Sep 19, 2014 at 09:04:08PM +0200, Dennis Jacobfeuerborn wrote: > > Hi, > > indeed after removing the option tcp-check line the checks now work as > > expected. Thanks for the pointer. > > Hey guys, no, that's a bug. Look at what is written in the documentation > (which should always be the reference to know if something is expected or > not) : > > option tcp-check > Perform health checks using tcp-check send/expect sequences > ... > - no "tcp-check" directive : the health check only consists in a > connection > attempt, which remains the default mode. > > So this doesn't match what you're observing and it's not acceptable. I could > reproduce it, I'm now checking the cause and trying to fix it. What I can tell > is that the servers are probed, but the result is ignored. I don't know why > yet.
OK so I fixed this. And it now correctly reports L4 OK in case of success and not L7OK anymore. Regards, Willy