On Wed, Mar 27, 2019 at 01:59:59PM +0300, Максим Куприянов wrote: > Hi, everybody! Got a core on 1.9.5. >
Hello, How did it happened? Can you reproduce? Can you share the systemd log of the service so we can see the forking and leaving of the workers. Thanks. > Core was generated by `/usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p > /var/run/haproxy.pid'. > Program terminated with signal SIGABRT, Aborted. > #0 0x00007fe164fd0428 in raise () from /lib/x86_64-linux-gnu/libc.so.6 > (gdb) thread apply all bt > > Thread 1 (Thread 0x7fe1668c7180 (LWP 169672)): > #0 0x00007fe164fd0428 in raise () from /lib/x86_64-linux-gnu/libc.so.6 > #1 0x00007fe164fd202a in abort () from /lib/x86_64-linux-gnu/libc.so.6 > #2 0x00007fe1650127ea in ?? () from /lib/x86_64-linux-gnu/libc.so.6 > #3 0x00007fe16501b37a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 > #4 0x00007fe16501f53c in free () from /lib/x86_64-linux-gnu/libc.so.6 > #5 0x000055cee0588fc4 in mworker_catch_sigchld (sh=<optimized out>) at > src/haproxy.c:872 > #6 0x000055cee0618f7b in __signal_process_queue () at src/signal.c:90 > #7 0x000055cee058b3e7 in signal_process_queue () at > include/proto/signal.h:39 > #8 run_poll_loop () at src/haproxy.c:2643 > #9 run_thread_poll_loop (data=<optimized out>) at src/haproxy.c:2703 > #10 0x000055cee04e7088 in mworker_loop () at src/haproxy.c:930 > #11 main (argc=<optimized out>, argv=0x7ffff429aa28) at src/haproxy.c:3125 > Looks like it tried to remove a child which is not in the process list anymore, it's not supposed to happened. Can you share your configuration? Thanks. -- William Lallemand
