So on one of my local development machines haproxy started pegging the CPU at 100% `strace -T` on the process just shows:
... epoll_wait(0, {}, 200, 0) = 0 <0.000003> epoll_wait(0, {}, 200, 0) = 0 <0.000003> epoll_wait(0, {}, 200, 0) = 0 <0.000003> epoll_wait(0, {}, 200, 0) = 0 <0.000003> epoll_wait(0, {}, 200, 0) = 0 <0.000003> epoll_wait(0, {}, 200, 0) = 0 <0.000003> ... Opening it up with gdb, the backtrace shows: (gdb) bt #0 0x00007f4d18ba82a3 in __epoll_wait_nocancel () from /lib64/libc.so.6 #1 0x00007f4d1a570ebc in _do_poll (p=<optimized out>, exp=-1440976915) at src/ev_epoll.c:125 #2 0x00007f4d1a4d3098 in run_poll_loop () at src/haproxy.c:1737 #3 0x00007f4d1a4cf2c0 in main (argc=<optimized out>, argv=<optimized out>) at src/haproxy.c:2097 This is haproxy 1.7.0 on CentOS/7 Unfortunately I'm not sure what triggered it. -Patrick