On Tue, Apr 19, 2016 at 09:53:36PM +0300, Veiko Kukk wrote: > On 19/04/16 18:52, Willy Tarreau wrote: > >On Tue, Apr 19, 2016 at 04:15:08PM +0200, Willy Tarreau wrote: > >OK in fact it's different. Above we have a busy polling loop, which may > >very be caused by the buffer space miscalculation bug and which results > >in a process not completing its job until a timeout strikes. The link to > >the other report shows a normal polling with blocked signals. > > The processes that was created yesterday via soft reload, went 100% cpu > today. > > haproxy 29388 5.0 0.0 58772 11700 ? Rs Apr17 156:44 > /usr/sbin/haproxy -D -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -sf > 1997 > > Section from strace output: > (...)
this below : > epoll_wait(0, {}, 200, 0) = 0 > epoll_wait(0, {}, 200, 0) = 0 > epoll_wait(0, {}, 200, 0) = 0 > epoll_wait(0, {}, 200, 0) = 0 > epoll_wait(0, {}, 200, 0) = 0 is not good unfortunately. I'm assuming this is with 1.5.17, that's it ? If so we still have an issue :-/ Thanks! Willy