apache 2.0.46 : segmentation fault or hangs system

Hi,

a couple of weeks ago I upgraded our servers from 2.0.43 to 2.0.46.
Since then, child processes on our internal server either exit with a
segmentation fault or keep running but take all CPU power. Hanging
processes occur at a rate of about 5 per hour. As far as I can see the
URLs they are serving are not special and work fine with other child
processes - however, they are all proxy requests.

We are using two apache 2.0.46 is a proxy chain, the internal webserver
hands all requests to the external apache 2.0.46. The external apache
does not have that problem, however, when an error occurs connecting to
a remote site or when an invalid status line is received, I noticed it
does not exit cleanly and an 'invalid status line' error is received
also by the internal server.

I tried to SIGQUIT a hanging childprocess to get a core but it does not
respond ... Is there a way to make a child process core ( I didn't find
a core anywhere ) when receiving a segmentation fault ?

The systems are HPUX 11.0 .

Thanks in advance !

Peter.

--
Peter Van Biesen
Adj. Sysadmin V.F.S.I.P.H.

tel: +32 (0) 2 225 85 70
fax: +32 (0) 2 225 85 88
e-mail: peter.vanbiesen@vlafo.be

RE: apache 2.0.46 : segmentation fault or hangs system

Hi Peter,
When you do a tusc, do you see the process looping on 'sendfile' ?.
If 'yes', I believe it's a transport layer bug (and we need some system
information), and I've been trying to duplicate it for the last couple of
months, without any success. It'll be nice if I can get access to the system
when the bug is showing up (I know it's a long shot). But, if that's not
possible, here are a couple of things that you might want to try :

1. Update to the latest ARPA and transport patches on your system
2. Use 'EnableSendFile off' in httpd.conf

Thanks
-Madhu

-----Original Message-----
From: Peter Van Biesen [mailto:peter.vanbiesen@vlafo.be]
Sent: Monday, June 30, 2003 2:19 AM
To: dev@httpd.apache.org; modproxy-dev@apache.org
Subject: apache 2.0.46 : segmentation fault or hangs system


Hi,

a couple of weeks ago I upgraded our servers from 2.0.43 to 2.0.46.
Since then, child processes on our internal server either exit with a
segmentation fault or keep running but take all CPU power. Hanging
processes occur at a rate of about 5 per hour. As far as I can see the
URLs they are serving are not special and work fine with other child
processes - however, they are all proxy requests.

We are using two apache 2.0.46 is a proxy chain, the internal webserver
hands all requests to the external apache 2.0.46. The external apache
does not have that problem, however, when an error occurs connecting to
a remote site or when an invalid status line is received, I noticed it
does not exit cleanly and an 'invalid status line' error is received
also by the internal server.

I tried to SIGQUIT a hanging childprocess to get a core but it does not
respond ... Is there a way to make a child process core ( I didn't find
a core anywhere ) when receiving a segmentation fault ?

The systems are HPUX 11.0 .

Thanks in advance !

Peter.

--
Peter Van Biesen
Adj. Sysadmin V.F.S.I.P.H.

tel: +32 (0) 2 225 85 70
fax: +32 (0) 2 225 85 88
e-mail: peter.vanbiesen@vlafo.be

Re: apache 2.0.46 : segmentation fault or hangs system

I'm sorry, tusc does not produce any output, the process just hangs and
eats all cpu. Possibly the process is not doing any systemcalls ? Output :

brussel6#tusc 15721
( Attached to process 15721 ("/opt/httpd/bin/httpd -k start -DSSL")
[32-bit] )
In user-mode
............................................................ ............................................................ ...
[running]
( Detaching from process 15721 ("/opt/httpd/bin/httpd -k start -DSSL") )
brussel6#

Processes that do not hang, exit on a segmentation fault or a bus error
but no core ... :-((

Peter.


MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote:

>Hi Peter,
> When you do a tusc, do you see the process looping on 'sendfile' ?.
>If 'yes', I believe it's a transport layer bug (and we need some system
>information), and I've been trying to duplicate it for the last couple of
>months, without any success. It'll be nice if I can get access to the system
>when the bug is showing up (I know it's a long shot). But, if that's not
>possible, here are a couple of things that you might want to try :
>
>1. Update to the latest ARPA and transport patches on your system
>2. Use 'EnableSendFile off' in httpd.conf
>
>Thanks
>-Madhu
>
>-----Original Message-----
>From: Peter Van Biesen [mailto:peter.vanbiesen@vlafo.be]
>Sent: Monday, June 30, 2003 2:19 AM
>To: dev@httpd.apache.org; modproxy-dev@apache.org
>Subject: apache 2.0.46 : segmentation fault or hangs system
>
>
>Hi,
>
>a couple of weeks ago I upgraded our servers from 2.0.43 to 2.0.46.
>Since then, child processes on our internal server either exit with a
>segmentation fault or keep running but take all CPU power. Hanging
>processes occur at a rate of about 5 per hour. As far as I can see the
>URLs they are serving are not special and work fine with other child
>processes - however, they are all proxy requests.
>
>We are using two apache 2.0.46 is a proxy chain, the internal webserver
>hands all requests to the external apache 2.0.46. The external apache
>does not have that problem, however, when an error occurs connecting to
>a remote site or when an invalid status line is received, I noticed it
>does not exit cleanly and an 'invalid status line' error is received
>also by the internal server.
>
>I tried to SIGQUIT a hanging childprocess to get a core but it does not
>respond ... Is there a way to make a child process core ( I didn't find
>a core anywhere ) when receiving a segmentation fault ?
>
>The systems are HPUX 11.0 .
>
>Thanks in advance !
>
>Peter.
>
>
>

--
Peter Van Biesen
Adj. Sysadmin V.F.S.I.P.H.

tel: +32 (0) 2 225 85 70
fax: +32 (0) 2 225 85 88
e-mail: peter.vanbiesen@vlafo.be