Hello Tomas,
On Sun, Jun 30, 2013 at 07:02:04PM +0200, Tomas Pospisek wrote:
> Hello everybody,
>
> shortly after starting haproxy on one of our servers, haproxy goes to
> 100% and stays there.
Hmmm not fun :-/
> We have multiple instances of haproxy running on various servers, but
> only one instance is consistently running at 100%.
Ah that's interesting.
> We are running
>
> * 3 instances with 1.4.24-1~bpo70+1 (Debian wheezy-backports)
> * 2 instances with 1.4.18-0ubuntu1.2 (Ubuntu precise)
>
> However only the one Debian instance is having the problem.
>
> Note that haproxy 1.4.24-1~bpo70+1 should contain the latest CPU related
> fixes discussed here.
>
> When I strace that instance, it's showing lots and lots of:
>
> epoll_wait(0, {}, 200, 0) = 0
Is it the only output for epoll_wait() or do you also see some values
where the timeout is non-zero (the last field) ? If it's always this,
then it probably means that a task supposed to run does not correctly
run or does not sleep.
Could you please try to run it with "nosepoll" in the global section ?
It will disable the speculative epoll and use only epoll. Can you
confirm that you don't have any health checks in your config ?
Health-checks are a good examle of a background task. I'm trying
to understand what could happen...
Other than that, I'm not thinking about anything that could induce
this. If you can, please try to disable the transparent proxy. We
could imagine that it reports an error very early that is not
properly caught and that causes the process to loop until a connect
timeout for example.
Thanks,
Willy
