Sorry only just got around to looking at this and updating my blog entry: Yes the important bit missing was "agent-check"....
But my testing with Dev21 seems to bring the servers back fine with any percentage reading i.e. 10% 75% etc. Please let me know if anyone else is having an issue, thanks. server Win2008R2 192.168.64.50:3389 weight 100 check agent-check agent-port 3333 inter 2000 rise 2 fall 3 minconn 0 maxconn 0 on-marked-down shutdown-sessions On 27 December 2013 22:44, PiBa-NL <piba.nl....@gmail.com> wrote: > Simon Drake schreef op 27-12-2013 17:07: > > > > Would it be possible to post an example showing the correct haproxy config > to use with the agent-check. > > By the way I saw the mailing list post recently about the changes to the > agent-check, using state and percentage, and I think that the right way to > go. > > For me this config works: > server MyServer 192.168.0.40:80 check inter 5000 agent-check > agent-inter 3333 agent-port 2123 weight 32 > > I've tried a few small tests with it, and while bringing a server to 'down' > or 'drain' seemed to work, i was missing the 'up' keyword, only "100%" seems > to bring a server back alive. So if your monitoring 100-%CPUusage and > sending that 1on1 back to the agent on a server with 99% cpu capacity > available wont come back up.. -- Regards, Malcolm Turnbull. Loadbalancer.org Ltd. Phone: +44 (0)870 443 8779 http://www.loadbalancer.org/
