Hi Praveen, On Thu, Jul 05, 2018 at 04:13:25PM +0000, UPPALAPATI, PRAVEEN wrote: > > > Hi Haproxy Team, > > Our Prod Haproxy instance is crashing with following error in > /var/log/messages: > > Jun 28 17:52:30 zlp32359 kernel: haproxy[55940]: segfault at 60 ip > 000000000045b0a9 sp 00007f4ef6b9f010 error 4 in haproxy[400000+12b000] > Jun 28 17:56:01 zlp32359 systemd: Started Session 73792 of user root. > Jun 28 17:56:01 zlp32359 systemd: Starting Session 73792 of user root. > Jun 28 17:56:01 zlp32359 LMC: Hardware Manufacturer = VMWARE > Jun 28 17:56:01 zlp32359 LMC: Hardware Product Name = VMware Virtual Platform > Jun 28 17:56:01 zlp32359 LMC: Hardware Serial # = VMware-42 29 ea 5e 6c 7b 5b > 49-ca 32 48 fb 5a 9d e7 d6 > Jun 28 17:56:01 zlp32359 LMC: ### NO PID_MAX ISSUES FOUND ### > Jun 28 17:56:01 zlp32359 LMC: ### NO READ ONLY FILE SYSTEM ISSUES FOUND ### > Jun 28 17:56:01 zlp32359 LMC: ### NO SCSI ABORT ISSUES FOUND ### > Jun 28 17:56:02 zlp32359 LMC: ### NO SCSI ERROR ISSUES FOUND ### > > HaProxyVersion: > > haproxy -v > HA-Proxy version 1.8.4-1deb90d 2018/02/08
Well, as you can see, at least 109 bugs have been fixed since this version, including one critical and 11 major, all potentially able to provoke a crash : http://www.haproxy.org/bugs/bugs-1.8.4.html I think it's *really* time for you to apply maintenance updates and try again. Regards, Willy
