Hello Willy ,

@Baptiste:
iptables  are nor running , irqbalance is running.  Will send the 100% CPU
load haproxy stats snapshot, today when load is about to reach peak.

@Willy:
Certainly will go ahead with upgrade.
>http://t55696.web-haproxy.webtalks.info/100-cpu-load-t55696.html
as mentioned on the link :
noslice
noepoll

Can it be useful for us too?

>You're running in server-close mode. Maybe you're having an improperly
>tuned conntrack on the machine which uses lots of CPU once the table is
>full for example.
We have disabled the conntrack on servers. With iptables Not running. Is
there anywhere it need to be taken care of?



On Thu, Mar 19, 2015 at 8:57 PM, Willy Tarreau <[email protected]> wrote:

> On Thu, Mar 19, 2015 at 02:00:14PM +0100, Baptiste wrote:
> > On Thu, Mar 19, 2015 at 1:37 PM, Saurab t <[email protected]>
> wrote:
> > > Hello Willy,
> > >
> > > Thanks you for your kind response.
> > >
> > > Here are the information required ::::
> > >
> > > Haproxy version :
> > > HA-Proxy version 1.5.8 2014/10/31
> > > Copyright 2000-2014 Willy Tarreau <[email protected]>
> > >
> > >
> > >
> > > If this can help As you have already responded to two other scenarios :
> > >
> > > http://www.serverphorums.com/read.php?10,1075864
> > >
> > > http://t55696.web-haproxy.webtalks.info/100-cpu-load-t55696.html
> > >
> > > how can we "exactly" trace if we have issue similar.
>
> You could be running the same bug as the first one given that it was
> fixed in 1.5.9 and you're still on 1.5.8. You need to stay up to date
> first. Please upgrade to 1.5.11 and see if the problem is still present.
> Anyway, the problem described above was related to long regex files, but
> you don't seem to be using that at all.
>
> Please send an output of either the stats page or of "show stats" on the
> CLI so that we get an idea of the request rate.
>
> You're running in server-close mode. Maybe you're having an improperly
> tuned conntrack on the machine which uses lots of CPU once the table is
> full for example.
>
> Regards
> Willy
>
>

Reply via email to