--001636c9254553719c0470a6e9b1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I just moved my website algebra.com, from my old trusty Fedora 3 server, to
my brand new Ubuntu Hardy server. The Hardy server is fully patched.

In the logs, I see a lot of error messages saying

segmentation fault

in the error.log file. No other details like pids, etc are provided.

~==>apache2 -v
Server version: Apache/2.2.8 (Ubuntu)
Server built: Jul 10 2009 18:41:09

I have no way to understand where these messages are from, how to debug the
fault, etc.

Any ideas? I have used linux for 14 years and would like to troubleshoot
this problem.,

--001636c9254553719c0470a6e9b1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I just moved my website <a href=3D"http://algebra.com">algebra.com</a>, fro=
m my old trusty Fedora 3 server, to my brand new Ubuntu Hardy server. The H=
ardy server is fully patched. <br><br>In the logs, I see a lot of error mes=
sages saying<br>
<br>segmentation fault<br><br>in the error.log file. No other details like =
pids, etc are provided. <br><br>~=3D=3D>apache2 -v<br>Server version: Ap=
ache/2.2.8 (Ubuntu)<br>Server built:=A0=A0 Jul 10 2009 18:41:09<br><br>I ha=
ve no way to understand where these messages are from, how to debug the fau=
lt, etc. <br>
<br>Any ideas? I have used linux for 14 years and would like to troubleshoo=
t this problem.,<br>

--001636c9254553719c0470a6e9b1--

--001636c5b06507bbb90470c1b9ce
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Sun, Aug 9, 2009 at 7:08 AM, Nick Wellnhofer <wellnhofer [at] aevum.de> wrote:

> Igor Chudov wrote:
> > In the logs, I see a lot of error messages saying: segmentation fault
> Are you using the worker MPM? If yes, try the prefork MPM instead.
>

Nick, thank you, per your advice, I did try using prefork MPM.

Unfortunately, the end result was still the same, a lot of segmentation
faults after a while.

The symptom is always the same, it runs great for a while (like maybe half
an hour) and then begins to give segmentation faults.
However, no matter what pages of my site I visit at this time, they all
display correctly.

I also ran apache2 with -X flag under GDB. I disabled SIGPIPE handling.

Again, it ran for an hour and crashed. However, when I tried to say "where"
in GDB, GDB told me that the process no longer exists.

i

--001636c5b06507bbb90470c1b9ce
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Sun, Aug 9, 2009 at 7:08 AM, Nick Wel=
lnhofer <span dir=3D"ltr"><<a href=3D"mailto:wellnhofer [at] aevum.de">wellnh=
ofer [at] aevum.de</a>></span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex=
; padding-left: 1ex;">
<div class=3D"im">Igor Chudov wrote:<br>
> In the logs, I see a lot of error messages saying: segmentation fault<=
br>
</div>Are you using the worker MPM? If yes, try the prefork MPM instead.<br=
></blockquote><div><br>Nick, thank you, per your advice, I did try using pr=
efork MPM. <br>
<br>
Unfortunately, the end result was still the same, a lot of segmentation fau=
lts after a while. <br>
<br>
The symptom is always the same, it runs great for a while (like maybe
half an hour) and then begins to give segmentation faults. <br>
However, no matter what pages of my site I visit at this time, they all dis=
play correctly.<br><br>
I also ran apache2 with -X flag under GDB. I disabled SIGPIPE handling. <br=
>
<br>
Again, it ran for an hour and crashed. However, when I tried to say
"where" in GDB, GDB told me that the process no longer exists. <b=
r>
<br>
i<br>
<br>=A0
<br></div></div><br>

--001636c5b06507bbb90470c1b9ce--

Igor Chudov wrote:
>
>
> On Sun, Aug 9, 2009 at 7:08 AM, Nick Wellnhofer <wellnhofer [at] aevum.de
> <mailto:wellnhofer [at] aevum.de>> wrote:
>
> Igor Chudov wrote:
> > In the logs, I see a lot of error messages saying: segmentation fault
> Are you using the worker MPM? If yes, try the prefork MPM instead.
>
>
> Nick, thank you, per your advice, I did try using prefork MPM.
>
> Unfortunately, the end result was still the same, a lot of segmentation
> faults after a while.
>
> The symptom is always the same, it runs great for a while (like maybe
> half an hour) and then begins to give segmentation faults.
> However, no matter what pages of my site I visit at this time, they all
> display correctly.
>
> I also ran apache2 with -X flag under GDB. I disabled SIGPIPE handling.
>
> Again, it ran for an hour and crashed. However, when I tried to say
> "where" in GDB, GDB told me that the process no longer exists.
>

Have you read this section of the docmentation on perl.apache.org?

http://perl.apache.org/docs/2.0/devel/debug/c.html

particularly the stuff about generating core dumps and analyzing them

Adam