I've brought up this bug before
(http://marc.info/?l=haproxy&m=139312718801838), but it seems to not
have gotten any attention, so I'm raising it again.
There is an issue with haproxy mis-reporting layer 4 checks. There are
2, likely related, issues.
1) When haproxy first starts up, it will report the server as "UP 1/3"
for however long the check interval is set to. If the interval is 30
seconds, it will say "UP 1/3" for 30 seconds.
2) Haproxy is adding the check interval time to the time of the check
itself. For example, if I have a check interval of 30 seconds, the
statistics output reports a check completion time of 30001ms.
Attached is a simple configuration that can be used to demonstrate this
issue. Launch haproxy, and then go to http://localhost/haproxy/stats
-Patrick
global
log 127.0.0.1 local0
defaults
log global
mode http
option httplog
timeout connect 5000
timeout client 60000
timeout server 170000
stats enable
stats uri /haproxy/stats
frontend f1
bind 0.0.0.0:9000
default_backend b1
backend b1
server s1 localhost:9001 check inter 10000
frontend f2
bind 0.0.0.0:9001
