Thanks Alex for the info. Unfortunately, I'm already using 'option
httpclose'. Here's my current cfg:
global
log 127.0.0.1 local0
log 127.0.0.1 local1 notice
#log loghost local0 info
maxconn 4096
#debug
#quiet
user haproxy
group haproxy
defaults
log global
mode http
option httplog
option dontlognull
retries 3
redispatch
maxconn 2000
contimeout 5000
clitimeout 50000
srvtimeout 50000
listen webfarm 192.168.31.100:80
mode http
stats enable
stats auth netadmin:5bgr+bdd1WbA
stats refresh 5s
balance roundrobin
cookie JSESSIONID prefix
option httpclose
option forwardfor
option httpchk HEAD /check.txt HTTP/1.0
server web1 192.168.31.202:80 cookie w01 check inter 2000 rise 2 fall
2
server web2 192.168.31.212:80 cookie w02 check inter 2000 rise 2 fall
2
option persist
redispatch
contimeout 5000
I will read the documentation again. I honestly did read it before.
Thanks, Tom
-----Original Message-----
From: Alex Forrow [mailto:[email protected]]
Sent: Wednesday, May 13, 2009 12:22 PM
To: [email protected]
Cc: [email protected]
Subject: Re: New HAProxy user keeps loosing connection
Hi Tom,
This sounds like a keep-alive issue.
HAProxy currently does not support connections that use HTTP keep-alive, in
that HAProxy will only process the first header sent in a connection, the
rest is considered data. Have a read of section 1 of the documentation for
more information on this.
If this is the problem, you can fix it using 'option httpclose' in you
HAProxy configuration, or by disabling keep-alives on your backend web
servers.
- Alex
Tom Potwin wrote:
>
> Hi
>
> I hope I'm doing this correctly. I just joined, and I haven't used a
> mailing list in a long time.
>
> I'm using HAProxy and Heartbeat on two Ubuntu 8.04 servers. I have two
> Xen nodes on each of my physical machines. One is the load balance and
> Heartbeat, the other is the actual web server. testing
> HAProxy/Heartbeat setup seems that it's working fine, but I keep
> loosing access to the HAProxy stats page. I know that isn't a huge
> problem, but I'm worried it might be a sign of a bigger problem
> somewhere.
>
> I just tried it again, and for a short time, I can see the stats just
> fine, then they're gone. I check the apache error log and I see this:
>
> File does not exist: /var/www/apache2-default/haproxy
>
> If I go back to my LB1 node and restart Heartbeat, it all comes back.
> I was hoping someone might recognize this behavior, and point me in
> the right direction.
>
> Thanks.
>
