Hi, On Sun, Oct 18, Daren Sefcik wrote: > I have an ICAP server backend with servers that each listen on different > ports, can anyone offer some advice on how to configure health checks for > it? I am currently using basic but that really doesn't help if the service > is not responding. > > Here is my haproxy config for the backend: > > backend HTPL_CONT_FILTER_tcp_ipvANY > mode tcp > balance roundrobin > timeout connect 50000 > timeout server 50000 > retries 3 > server HTPL-WEB-01_10.1.4.153 10.1.4.153:1344 check inter 5000 weight 200 > maxconn 200 fastinter 1000 fall 5 > server HTPL-WEB-02_10.1.4.154 10.1.4.154:1344 check inter 5000 weight 200 > maxconn 200 fastinter 1000 fall 5 > server HTPL-WEB-02_10.1.4.155_01 10.1.4.155:8102 check inter 5000 weight > 200 maxconn 200 fastinter 1000 fall 5 > server HTPL-WEB-02_10.1.4.155_02 10.1.4.155:8202 check inter 5000 weight > 200 maxconn 200 fastinter 1000 fall 5
Do the icap servers (squid+diladele?) respond to something like this: https://support.symantec.com/en_US/article.TECH220980.html or https://exchange.icinga.org/oldmonex/1733-check_icap.pl/check_icap.pl Maybe you can use tcp-check to send icap request and look for "ICAP/1.0 200" response: https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#tcp-check%20connect http://blog.haproxy.com/2014/01/02/haproxy-advanced-redis-health-check/ -Jarno -- Jarno Huuskonen
