Hi. Am 12.02.2019 um 18:36 schrieb Mildis: > Hi list, > > haproxy is segfaulting multiple times these days for no apparent reason. > At first i thought is was a load issue but even few RPS made it crash. > > Symptoms are always the same : segfault of a worker then spawn of a new. > If load is very high, spawned worker segfault immediatly. > > In the messages log, the offset is always the same (+1e2000). > > I'm running 1.9.4 (from vincent bernat package) in Debian stretch. > > In haproxy logs : > Feb 12 11:36:54 ns3089939 haproxy: [ALERT] 042/113654 (32688) : > Current worker #1 (32689) exited with code 139 (Segmentation fault) > Feb 12 11:36:54 ns3089939 haproxy: [ALERT] 042/113654 (32688) : > exit-on-failure: killing every workers with SIGTERM > Feb 12 11:36:54 ns3089939 haproxy: [WARNING] 042/113654 (32688) : All > workers exited. Exiting... (139) > > In /var/log/messages > kernel: traps: haproxy general protection ip:561e5b799375 > sp:7ffe6fd3f2f0 error:0 in haproxy[561e5b72d000+1e2000] > > "show errors" is empty. > > How could I diagnose further without impacting production too much ?
Can you activate coredumps ulimit -c unlimited you should find the core in /tmp or just search for core on the filesystem You can get a backtrace with the following command as soon as you have a coredump gdb /usr/sbin/haproxy #YOUR_CORE_FILE# bt full > Thanks, > mildis Regards aleks