Willy Tarreau a écrit :
>> The tarball you mention at the end of your answer seems to work well. >> But, there is still a problem with server ceck and i don't know if it is >> due to haproxy or something else on my network. If y configure a check >> interval less than 10s, it works.
no, less than 10s. e.g., check inter 10000 fall 4 rise 1 works while check inter 20000 fall 4 rise 1 gives the strange behaviour i mention.
> I have never seen such a strange behaviour! The checks are so simple, I
> would not even imagine what could cause this! Would you happen to have
> ip_conntrack loaded on the machine hosting haproxy ?
ip_conntrack is enabled (it must be since i use openvz virtualization).
> It would be possible
> that when it runs, the conntrack table slowly fills, and that once full,
> haproxy simply cannot establish new connections to the servers, resulting
> in them being seen as down.
Well, if it the case the check should work better when check interval is
greater, shouldn't it?
> It is also possible that anything between haproxy and the servers is causing
> this. You may want to experiment with the check interval to see if the
> problem appears in a delay proportionnal to the interval.
There is one thing really strange : i've checked the network traffic
with tcpdump and i can see the check requests of haproxy arriving on the
backend, and i also can see the response send by the backend.
I'll check if haproxy receive the response.
Florian Received on 2008/02/15 09:12
This archive was generated by hypermail 2.2.0 : 2008/02/15 09:15 CET