Re: Squid Backend Health Checks

2015-10-14 Thread Daren Sefcik 
The only thing I can look at is the stats page which report failed health
checks. I have tried to configure pfsense to log things but have been
unsuccessful. Any insight how to configure logging in pfsense would be
really appreciated.

On Wed, Oct 14, 2015 at 7:08 AM, Baptiste  wrote:

> Hi Daren,
>
> What type of errors are reported?
>
> Baptiste
>
> On Wed, Oct 14, 2015 at 8:19 AM, Daren Sefcik 
> wrote:
> > I followed Willy's advice from this post
> >
> > http://www.mail-archive.com/haproxy@formilux.org/msg05171.html
> >
> > but seem to get a lot of health check errors and (false) Dwntme. Is
> there a
> > newer or better way to do health checks or am I missing something?
> >
> > TIA..
> >
> > BTW, nice work on 1.6, am looking forward to trying it out soon...
> >
> >
> > Here is my relevant code, http://10.1.4.105:9090 is the CARP address my
> > clienst also use as the proxy ip to use. I tried using the local IP and
> had
> > the same problems.
> >
> > listen check-responder
> > bind *:9090
> > mode http
> > monitor-uri /
> > timeout client 5000
> > timeout connect 5000
> > timeout server 5000
> >
> >
> > backend HTPL_WEB_PROXY_http_ipvANY
> > mode http
> > stick-table type ip size 50k expire 5m
> > stick on src
> > balance roundrobin
> > timeout connect 5
> > timeout server 5
> > retries 3
> > option httpchk GET http://10.1.4.105:9090/ HTTP/1.0
> > server HTPL-PROXY-01_10.1.4.103 10.1.4.103:3128 cookie HTPLPROXY01 check
> > inter 3  weight 175 maxconn 1500 fastinter 1000 fall 5
> > server HTPL-PROXY-02_10.1.4.104 10.1.4.104:3128 cookie HTPLPROXY02 check
> > inter 3  weight 175 maxconn 1500 fastinter 1000 fall 5
> > server HTPL-PROXY-03_10.1.4.107 10.1.4.107:3128 cookie HTPLPROXY03 check
> > inter 3  weight 100 maxconn 1500 fastinter 1000 fall 5
> > server HTPL-PROXY-04_10.1.4.108 10.1.4.108:3128 cookie HTPLPROXY04 check
> > inter 3  weight 200 maxconn 1500 fastinter 1000 fall 5
> > server HTHPL-PROXY-02_10.1.4.101 10.1.4.101:3128 cookie HTHPLPROXY02
> check
> > inter 3  weight 150 maxconn 1500 fastinter 1000 fall 5
> > server HTHPL-PROXY-03_10.1.4.102 10.1.4.102:3128 cookie HTHPLPROXY03
> check
> > inter 3  weight 125 maxconn 1000 fastinter 1000 fall 5
> >
> >
>

Re: Squid Backend Health Checks

2015-10-14 Thread Daren Sefcik 
Using HATop I see lots of ERSP errors which I guess is response
errors...not sure if that is helpful.

On Wed, Oct 14, 2015 at 7:40 AM, Daren Sefcik 
wrote:

> The only thing I can look at is the stats page which report failed health
> checks. I have tried to configure pfsense to log things but have been
> unsuccessful. Any insight how to configure logging in pfsense would be
> really appreciated.
>
> On Wed, Oct 14, 2015 at 7:08 AM, Baptiste  wrote:
>
>> Hi Daren,
>>
>> What type of errors are reported?
>>
>> Baptiste
>>
>> On Wed, Oct 14, 2015 at 8:19 AM, Daren Sefcik 
>> wrote:
>> > I followed Willy's advice from this post
>> >
>> > http://www.mail-archive.com/haproxy@formilux.org/msg05171.html
>> >
>> > but seem to get a lot of health check errors and (false) Dwntme. Is
>> there a
>> > newer or better way to do health checks or am I missing something?
>> >
>> > TIA..
>> >
>> > BTW, nice work on 1.6, am looking forward to trying it out soon...
>> >
>> >
>> > Here is my relevant code, http://10.1.4.105:9090 is the CARP address my
>> > clienst also use as the proxy ip to use. I tried using the local IP and
>> had
>> > the same problems.
>> >
>> > listen check-responder
>> > bind *:9090
>> > mode http
>> > monitor-uri /
>> > timeout client 5000
>> > timeout connect 5000
>> > timeout server 5000
>> >
>> >
>> > backend HTPL_WEB_PROXY_http_ipvANY
>> > mode http
>> > stick-table type ip size 50k expire 5m
>> > stick on src
>> > balance roundrobin
>> > timeout connect 5
>> > timeout server 5
>> > retries 3
>> > option httpchk GET http://10.1.4.105:9090/ HTTP/1.0
>> > server HTPL-PROXY-01_10.1.4.103 10.1.4.103:3128 cookie HTPLPROXY01
>> check
>> > inter 3  weight 175 maxconn 1500 fastinter 1000 fall 5
>> > server HTPL-PROXY-02_10.1.4.104 10.1.4.104:3128 cookie HTPLPROXY02
>> check
>> > inter 3  weight 175 maxconn 1500 fastinter 1000 fall 5
>> > server HTPL-PROXY-03_10.1.4.107 10.1.4.107:3128 cookie HTPLPROXY03
>> check
>> > inter 3  weight 100 maxconn 1500 fastinter 1000 fall 5
>> > server HTPL-PROXY-04_10.1.4.108 10.1.4.108:3128 cookie HTPLPROXY04
>> check
>> > inter 3  weight 200 maxconn 1500 fastinter 1000 fall 5
>> > server HTHPL-PROXY-02_10.1.4.101 10.1.4.101:3128 cookie HTHPLPROXY02
>> check
>> > inter 3  weight 150 maxconn 1500 fastinter 1000 fall 5
>> > server HTHPL-PROXY-03_10.1.4.102 10.1.4.102:3128 cookie HTHPLPROXY03
>> check
>> > inter 3  weight 125 maxconn 1000 fastinter 1000 fall 5
>> >
>> >
>>
>
>

Squid Backend Health Checks

2015-10-14 Thread Daren Sefcik 
I followed Willy's advice from this post

http://www.mail-archive.com/haproxy@formilux.org/msg05171.html

but seem to get a lot of health check errors and (false) Dwntme. Is there a
newer or better way to do health checks or am I missing something?

TIA..

BTW, nice work on 1.6, am looking forward to trying it out soon...


Here is my relevant code, http://10.1.4.105:9090 is the CARP address my
clienst also use as the proxy ip to use. I tried using the local IP and had
the same problems.

listen check-responder
bind *:9090
mode http
monitor-uri /
timeout client 5000
timeout connect 5000
timeout server 5000


backend HTPL_WEB_PROXY_http_ipvANY
mode http
stick-table type ip size 50k expire 5m
stick on src
balance roundrobin
timeout connect 5
timeout server 5
retries 3
option httpchk GET http://10.1.4.105:9090/ HTTP/1.0
server HTPL-PROXY-01_10.1.4.103 10.1.4.103:3128 cookie HTPLPROXY01 check
inter 3  weight 175 maxconn 1500 fastinter 1000 fall 5
server HTPL-PROXY-02_10.1.4.104 10.1.4.104:3128 cookie HTPLPROXY02 check
inter 3  weight 175 maxconn 1500 fastinter 1000 fall 5
server HTPL-PROXY-03_10.1.4.107 10.1.4.107:3128 cookie HTPLPROXY03 check
inter 3  weight 100 maxconn 1500 fastinter 1000 fall 5
server HTPL-PROXY-04_10.1.4.108 10.1.4.108:3128 cookie HTPLPROXY04 check
inter 3  weight 200 maxconn 1500 fastinter 1000 fall 5
server HTHPL-PROXY-02_10.1.4.101 10.1.4.101:3128 cookie HTHPLPROXY02 check
inter 3  weight 150 maxconn 1500 fastinter 1000 fall 5
server HTHPL-PROXY-03_10.1.4.102 10.1.4.102:3128 cookie HTHPLPROXY03 check
inter 3  weight 125 maxconn 1000 fastinter 1000 fall 5