Hi,
Le 12/02/2015 21:23, chris...@endlessnow.com a écrit :
Is there a problem with health checks and haproxy? Again, using a
machine
gun approach on the health check service, we see no problems, but for
whatever reason, occasionally (maybe 1 out 10, could be more), the
haproxy
tcp expect fails. Using tcpdump, seems we're getting the right return
though.
Can you share that tcpdump?
That one is harder to share, difficult to sanitize.
We're using haproxy 1.15 without pcre expressions.
There is no such release. What release are you running exactly?
Dyslexia I guess... I meant 1.5.10
Management is saying we're going to drop haproxy for nginx-plus because of
this problem.... so last chance if anyone has any ideas on this.
Why not changing "Management" ? ;-)
I think you're not using healthchecks the right way.
Prefer "option httpchk" to "option tcp-check" combined "tcp-check send",
and prefer "http-check expect" instead of "tcp-check expect".
Also, try to upgrade to haproxy 1.5.11 or at least, add a "Connection:
close" header in your check.
http://www.haproxy.org/git?p=haproxy-1.5.git;a=commit;h=a448e16da00374b39ae30d6f5595d4060b140f17
Last, keep in mind that haproxy will only check strings that feet in the
buffer.
Without any logs, it's difficult to say which case you're encountering.
(have a feeling that unless an "idea" and/or "fix" comes today, that it
will too late though... but feel free to respond anyhow.... maybe it will
help somebody else!)
--
Cyril Bonté
