We've been running haproxy 1.8 series for quite a while.  We're currently
in the process of updating to 2.1, and have installed from the vbernat PPA
on Ubuntu 18.04 using the same old config file.

Now we are seeing segfaults a few times a day:

Mar 03 14:53:52 fw1.dev.realgo.com kernel: haproxy[8654]: segfault at 18 ip
000056389a674d08 sp 00007fac18dba030 error 4 in haproxy[56389a52b000+235000]
Mar 03 14:53:52 fw1.dev.realgo.com haproxy[8649]: [ALERT] 062/145352 (8649)
: Current worker #1 (8653) exited with code 139 (Segmentation fault)
Mar 03 14:53:52 fw1.dev.realgo.com haproxy[8649]: [ALERT] 062/145352 (8649)
: exit-on-failure: killing every processes with SIGTERM
Mar 03 14:53:52 fw1.dev.realgo.com haproxy[8649]: [WARNING] 062/145352
(8649) : All workers exited. Exiting... (139)
Mar 03 14:53:52 fw1.dev.realgo.com systemd[1]: haproxy.service: Main
process exited, code=exited, status=139/n/a
Mar 03 14:53:52 fw1.dev.realgo.com systemd[1]: haproxy.service: Failed with
result 'exit-code'.

Looks like it is restarting 5-10 times a day during the work week, less
during the weekend where only our monitoring system is hitting it.

I haven't tried disabling htx, which the other recent Segfault thread said
resolved it.  I'm currently trying reverting down to 2.0.13.

I'm happy to provide the config if that helps.  It's 419 lines.

Sean

Reply via email to