------------------------------------------------------------------------ *From: *Willy Tarreau <w...@1wt.eu> *Sent: * 2014-04-11 08:29:15 E *To: *Patrick Hemmer <hapr...@stormcloud9.net> *CC: *haproxy@formilux.org *Subject: *Re: haproxy mis-reporting layer 4 checks
> Hi Patrick, > > On Thu, Apr 10, 2014 at 02:17:02PM -0400, Patrick Hemmer wrote: >> 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. > We used to have this bug in a certain version (I don't remember which > one), but I fail to reproduce it anymore with latest master using your > configuration. What version are you running ? > > Willy Ah, you're right. I was testing against 1.5-dev22. Using the latest master this is fixed. Sorry for the noise. -Patrick
