Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAL_7JRz44K9QzygPZWe310DC=CnfGn844U1dTaTfoUVDaGhS1Q@mail.gmail.com>
References: 
 <CAP=VsLTcZOdqixXZVYbY7=H1R+C-k_iPenLCWZV2cm2XO3mfrw@mail.gmail.com>
	<CAL_7JRz44K9QzygPZWe310DC=CnfGn844U1dTaTfoUVDaGhS1Q@mail.gmail.com>
Date: Sat, 22 Aug 2015 11:14:28 +1000
Message-ID: 
 <CAP=VsLQNrbh8+ADkrhv2XZtjQk9+i5ewCibkKE-3PCxdciYZ7w@mail.gmail.com>
From: Daryl King <allnatives.online@gmail.com>
To: users@httpd.apache.org
Content-Type: multipart/alternative; boundary=089e01494af01cb7dd051ddc1b68
Subject: Re: [users@httpd] apache segfault debugging with gdb - need advice

--089e01494af01cb7dd051ddc1b68
Content-Type: text/plain; charset=UTF-8

Thanks Ryan. Strangely when running "ulimit -n" it returns 65536 in a ssh
session, but 1024 in webmin? Which one would be correct?

On Sat, Aug 22, 2015 at 12:52 AM, R T <i.r.dshiznit@gmail.com> wrote:

>
> Hi Daryl,
>
> Typically when I see a core dump when running siege, it is a resource
> issue. Out of memory, and/or I've reached the ulimit on my machine and need
> to set it higher. The limit is 1024 (displayed via ulimit -n), and can be
> changed via ulimit -n <value>. This change isn't persistent - and the
> setting can be changed permanently by editing
> /etc/sysconfig/security/limits.conf.
>
> I typically set it to something unrealistically high, and the machine will
> always run out of memory before hitting the ulimit.
>
>
> - Ryan
>
> On Fri, Aug 21, 2015 at 9:49 AM, Daryl King <allnatives.online@gmail.com>
> wrote:
>
>> I am running Apache 2.4.10 with mpm_event on a Debian 8 vps. When I run
>> Siege on my setup it runs well, except for a Segmentaion Fault at the very
>> end [child pid xxxx exit signal Segmentation fault (11)]. I have run GDB on
>> a core dump of the segfault and returned this:
>>  [Using host libthread_db library
>> "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> Core was generated by `/usr/sbin/apache2 -k start'.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0  0x00007f53a4ac8add in read () at ../sysdeps/unix/syscall-template.S:81
>> 81    ../sysdeps/unix/syscall-template.S: No such file or directory.
>> (gdb)]
>> Im at a loss as to how to proceed with this, but am willing to keep
>> digging until I find the answer. Any advice appreciated..
>>
>
>

--089e01494af01cb7dd051ddc1b68
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Ryan. Strangely when running &quot;ulimit -n&quot; =
it returns 65536 in a ssh session, but 1024 in webmin? Which one would be c=
orrect?<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Sat, Aug 22, 2015 at 12:52 AM, R T <span dir=3D"ltr">&lt;<a href=3D"mail=
to:i.r.dshiznit@gmail.com" target=3D"_blank">i.r.dshiznit@gmail.com</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div=
><div><div><br></div>Hi Daryl,<br><br></div>Typically when I see a core dum=
p when running siege, it is a resource issue. Out of memory, and/or I&#39;v=
e reached the ulimit on my machine and need to set it higher. The limit is =
1024 (displayed via ulimit -n), and can be changed via ulimit -n &lt;value&=
gt;. This change isn&#39;t persistent - and the setting can be changed perm=
anently by editing /etc/sysconfig/security/limits.conf.<br><br></div>I typi=
cally set it to something unrealistically high, and the machine will always=
 run out of memory before hitting the ulimit. <br><br><br></div>- Ryan<br><=
/div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Fri, Aug 21, 2015 at 9:49 AM, Daryl King <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:allnatives.online@gmail.com" target=3D=
"_blank">allnatives.online@gmail.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div dir=3D"ltr"><div>I am running Apache 2.4.10 with mpm=
_event on a Debian 8 vps. When I run Siege on my setup it runs well, except=
 for a Segmentaion Fault at the very end [child pid xxxx exit signal Segmen=
tation fault (11)]. I have run GDB on a core dump of the segfault and retur=
ned this:<br>=C2=A0[Using host libthread_db library &quot;/lib/x86_64-linux=
-gnu/libthread_db.so.1&quot;.<br>Core was generated by `/usr/sbin/apache2 -=
k start&#39;.<br>Program terminated with signal SIGSEGV, Segmentation fault=
.<br>#0=C2=A0 0x00007f53a4ac8add in read () at ../sysdeps/unix/syscall-temp=
late.S:81<br>81=C2=A0=C2=A0=C2=A0 ../sysdeps/unix/syscall-template.S: No su=
ch file or directory.<br>(gdb)]<br></div>Im at a loss as to how to proceed =
with this, but am willing to keep digging until I find the answer. Any advi=
ce appreciated..<br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--089e01494af01cb7dd051ddc1b68--