Hello, Probably a useless report as I don't have a lot information to provide, but we faced an issue where the unix socket was unresponsive, with the processes using all cpu (1600% with 16 nbthreads)
I only have the backtrace of the main process but lost the backtrace of all threads (nbthread 16). I was also unable to get a response from the socket. (gdb) bt #0 0x00005636716d7fbe in fwrr_set_server_status_up (srv=0x5636928e6700) at src/lb_fwrr.c:112 #1 0x000056367162f8e7 in srv_update_status (s=0x5636928e6700) at src/server.c:4884 #2 0x000056367162f4f2 in server_recalc_eweight (sv=sv@entry=0x5636928e6700, must_update=must_update@entry=1) at src/server.c:1310 #3 0x000056367163845d in server_warmup (t=0x56369c969d40, context=0x5636928e6700, state=<optimized out>) at src/checks.c:1492 #4 0x00005636716cd802 in process_runnable_tasks () at src/task.c:437 #5 0x0000563671646ebf in run_poll_loop () at src/haproxy.c:2645 #6 run_thread_poll_loop (data=data@entry=0x563671fb5d20) at src/haproxy.c:2710 #7 0x00005636715be2f5 in main (argc=<optimized out>, argv=0x7fffdaa3b7f8) at src/haproxy.c:3346 note: this process is based v1.9.6 until 0b4b27efde653a4b7bbafb56df3796bffa4722ae on top of it. I will try to grab more information about it if we are seeing the issue again. -- William
