On Sat, Mar 13, 2010 at 11:28:19AM +0100, Anze wrote: > > no, your config is not clear to me now. Could you please post it ? > > Sorry, it was late. :) > > Here is my config: (I replaced all sensitive info, I hope I haven't made a > mistake)
OK it's a lot more clear now :-) > listen webfarm 123.123.123.123:80 > mode http > stats enable > balance roundrobin > stats auth user:pass > cookie SERVERID insert indirect > option httpclose > option forwardfor except 123.123.123.123 > # option httpchk HEAD /check.php HTTP/1.0 > # option httpchk /check.php > # http-check expect string all_is_ok > server a0 10.0.0.1:8080 cookie a0 check > server a1 10.0.0.2:8080 cookie a1 check > ----- > > I have played with the 3 uncommented lines in "listen" section - these are > the > results: > > With 1.4.1 WITHOUT patch: > - all 3 lines disabled: system works (serves content, no problem, but no > check) > - only 1. line enabled: system works (serves content, performs checks) > - only 2. line enabled: system works (serves content, performs checks) > > So the system works and it is correctly configured. > > With 1.4.1 WITH patch applied: > - all 3 lines disabled: system works (serves content, no problem, but no > check) > - only 1. line enabled: ERROR, haproxy tells all hosts are down (when they > are > not) > - only 2. line enabled: ERROR, haproxy tells all hosts are down (when they > are > not) > - 2. and 3. line or 1. and 3. line enabled: ERROR as above. > > Hope that clears things up... Any ideas? Not right now. I'm CCing Nick who's probably the one who knows the patch the best. Maybe he has an idea. What I suspect is that checks now only work when using expect. It's pretty common to test only the new feature and not older ones when developing something new, unfortunately. Thanks, Willy
