Le 20/07/2020 à 16:23, Sander Klein a écrit :
In the meantime I've captured a coredump. It gives the following output:
GNU gdb (Debian 8.2.1-2+b3) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from haproxy...Reading symbols from
/usr/lib/debug/.build-id/d7/b1ac9548a895bfb6276bb7491ae8d396835cf0.debug...done.
done.
[New LWP 1821]
[New LWP 1819]
[New LWP 1820]
[New LWP 1822]
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/haproxy -sf 453 -Ws -f
/etc/haproxy/conf.d -p /run/haproxy.pid -S /ru'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00005637136d3e27 in si_cs_send (cs=cs@entry=0x7fee40d97520) at
include/haproxy/channel.h:128
128 include/haproxy/channel.h: No such file or directory.
It seems pretty close to the issue #762
(https://github.com/haproxy/haproxy/issues/762). As suggested on GitHub, it may
be related to the bug fixed by the commit 273aea4.
Could you retry with the latest 2.2 snapshot
(http://www.haproxy.org/download/2.2/src/snapshot/haproxy-ss-LATEST.tar.gz) ?
--
Christopher Faulet
