Re: Incorrect counters in stats interface

> On 07 Sep 2016, at 23:12, David Birdsong wrote: > > Queue Cur is a gauge and so not representative of historical values. > > Queue Max of zero is telling though. > > In addition to queue timeout, there are other ways haproxy can synthesize an > http response on

Re: Incorrect counters in stats interface

Queue Cur is a gauge and so not representative of historical values. Queue Max of zero is telling though. In addition to queue timeout, there are other ways haproxy can synthesize an http response on behalf of the backend server. Check for connection errors. On Wed, Sep 7, 2016 at 12:15 PM

Re: Incorrect counters in stats interface

> On 07 Sep 2016, at 21:10, PiBa-NL wrote: > > Hi Dmitry, > Op 7-9-2016 om 15:54 schreef Dmitry Sivachenko: >> Hello, >> >> (sorry for reposting, but I do not see my e-mail in ML archive, so I assume >> it was blocked due to screenshots in attachments. I replace them

Re: Incorrect counters in stats interface

Hi Dmitry, Op 7-9-2016 om 15:54 schreef Dmitry Sivachenko: Hello, (sorry for reposting, but I do not see my e-mail in ML archive, so I assume it was blocked due to screenshots in attachments. I replace them with links now). I am using haproxy-1.6.9. In web stats interface, I mouse-over

Incorrect counters in stats interface

Hello, (sorry for reposting, but I do not see my e-mail in ML archive, so I assume it was blocked due to screenshots in attachments. I replace them with links now). I am using haproxy-1.6.9. In web stats interface, I mouse-over backend's Total Sessions counter (1728 in my case), and I see