On Saturday 13 March 2010, Willy Tarreau wrote:
> On Fri, Mar 12, 2010 at 11:55:59PM +0100, Anze wrote:
> > On Friday 12 March 2010, Willy Tarreau wrote:
> > > > > It is possible with the patch that Nick Chalk recently posted in
> > > > > the thread "Truncated health check response from real servers". It
> > > > > is a rework of an ...
> > > > > You seem to be a good candidate to test it :-)
> >
> > I'm having trouble getting this to work. Without "option httpchk" - no
> > problem. Then I try with the check and I get this:
>
> 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)
-----
global
log 127.0.0.1 local0
log 127.0.0.1 local1 notice
#log loghost local0 info
maxconn 4096
#chroot /usr/share/haproxy
user haproxy
group haproxy
daemon
#debug
#quiet
defaults
log global
mode http
option httplog
option dontlognull
retries 3
option redispatch
maxconn 2000
contimeout 5000
clitimeout 50000
srvtimeout 50000
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?
Anze
