Re: High CPU Usage followed by segfault error

2018-10-20 Thread Soji Antony
Hi FYI, following is the backtrace for segfault which we are seeing in the kern.log. Oct 18 10:11:30 kernel: [841364.001036] haproxy[30696]: segfault at 8 ip 5567eaf6aac2 sp 7ffdd70447b0 error 6 in haproxy[5567eae75000+172000] # apport-retrace -g _usr_sbin_haproxy.0.crash GNU gdb

Re: High CPU Usage followed by segfault error

2018-10-16 Thread Olivier Houchard
On Tue, Oct 16, 2018 at 05:02:30PM +0200, Willy Tarreau wrote: > On Tue, Oct 16, 2018 at 04:11:20PM +0200, Willy Tarreau wrote: > > Could you please apply the attached patch ? I'm going to merge it into 1.9 > > and we'll backport it to 1.8 later. > > And please add the attached one as well, which

Re: High CPU Usage followed by segfault error

2018-10-16 Thread Willy Tarreau
On Tue, Oct 16, 2018 at 04:11:20PM +0200, Willy Tarreau wrote: > Could you please apply the attached patch ? I'm going to merge it into 1.9 > and we'll backport it to 1.8 later. And please add the attached one as well, which is specific to 1.8. I suspect that different versions of compiler could

Re: High CPU Usage followed by segfault error

2018-10-16 Thread Willy Tarreau
Hi, On Tue, Oct 16, 2018 at 09:28:46AM +0530, Soji Antony wrote: > FYI, the initial version which we were using before upgrading to 1.8.14 > was 1.8.13. > By mistake updated it as 1.8.3 in my first email. No problem, thanks for the precision. After re-reading the code, I found a bug, which is

Re: High CPU Usage followed by segfault error

2018-10-16 Thread Olivier Houchard
Hi Soji, On Mon, Oct 15, 2018 at 11:10:09PM +0530, Soji Antony wrote: > Hi Olivier, > > Many thanks for your reply. > Please find the gdb output given below. > > # gdb /usr/sbin/haproxy core.dump3.13871 > GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1 > Copyright (C) 2014 Free Software

Re: High CPU Usage followed by segfault error

2018-10-15 Thread Soji Antony
FYI, the initial version which we were using before upgrading to 1.8.14 was 1.8.13. By mistake updated it as 1.8.3 in my first email. Thanks On Mon, Oct 15, 2018 at 11:10 PM Soji Antony wrote: > Hi Olivier, > > Many thanks for your reply. > Please find the gdb output given below. > > # gdb

Re: High CPU Usage followed by segfault error

2018-10-15 Thread Soji Antony
Hi Olivier, Many thanks for your reply. Please find the gdb output given below. # gdb /usr/sbin/haproxy core.dump3.13871 GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: High CPU Usage followed by segfault error

2018-10-15 Thread Olivier Houchard
Hi, On Sat, Oct 13, 2018 at 01:34:53PM +0530, Soji Antony wrote: > Really appreciate if some one can help with this issue. This is happening > quite frequently on our servers. I have taken a coredump when this happened > last time using 'gcore' command. However unable to share it as it might >

Re: High CPU Usage followed by segfault error

2018-10-12 Thread Soji Antony
Hi Oliver, Thanks for the suggestion. We have upgraded haproxy to 1.8.14 but seeing the same CPU issue again. I have found that the segmentation fault which we were seeing earlier is not related to the CPU spike as it is happening at different time. Recently we had the same issue with one of our

Re: High CPU Usage followed by segfault error

2018-10-02 Thread Olivier Houchard
Hi, On Tue, Oct 02, 2018 at 08:26:12PM +0530, Soji Antony wrote: > Hello, > > We are currently using haproxy 1.8.3 with single process multithreaded > configuration. > We have 1 process and 10 threads each mapped to a separate core [0-9]. We > are running our haproxy instances on a c4.4xlarge

High CPU Usage followed by segfault error

2018-10-02 Thread Soji Antony
Hello, We are currently using haproxy 1.8.3 with single process multithreaded configuration. We have 1 process and 10 threads each mapped to a separate core [0-9]. We are running our haproxy instances on a c4.4xlarge aws ec2 instance. The only other CPU intensive process running on this server is