Re: example of agent-check ?
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: serverMyServer 192.168.0.40:80 check inter 5000 agent-check agent-inter 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..
example of agent-check ?
Hi Guys, I have been looking at the agent-check functionality. I started out using windows agent, trunked haproxy code and the config example from Malcolm Turnbull here : http://blog.loadbalancer.org/open-source-windows-service-for-reporting-server-load-back-to-haproxy-load-balancer-feedback-agent/ However I saw the agent-check had been added to the latest build 1.5-dev21, so I have started using that.However the config example doesn't seem to want to work with the latest official * build. Haproxy doesnt moan about the config, but it doesnt seem to be using the check or logging any information about it.* *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.* *Thanks for your help and a great haproxy.* *Simon *
RE: [Help] How can I use haproxy with ssl
Hi, > My Linux is > [...] > Description: CentOS release 5.10 (Final) > [...] > and Installed openssl-1.0.1e Please decide now: would you like to use the openssl from your repository or do you want to build it on your own? There is no point in troubleshooting 2 different problems at the same time. Please always respond to the mailing list. Regards, Lukas