httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Caplan <michael.cap...@lechateau.ca>
Subject RE: [users@httpd] Strategies for debugging a segmentation fault o n a production ser ver
Date Tue, 21 Jun 2005 16:35:43 GMT
Marc,

That is exactly what I did originally.  No results though.  The log  is not
written to.

Thanks,

Michael


> -----Original Message-----
> From: Marc Wiatrowski [mailto:wia@iglass.net]
> Sent: Tuesday, June 21, 2005 9:32 AM
> To: users@httpd.apache.org
> Subject: RE: [users@httpd] Strategies for debugging a segmentation fault o
> n a production ser ver
> 
> 
> > > -----Original Message-----
> > > From: Krist van Besien [mailto:krist.vanbesien@gmail.com]
> > > Sent: Tuesday, June 21, 2005 8:22 AM
> > >
> > > > On 6/21/05, Michael Caplan <michael.caplan@lechateau.ca> wrote:
> > > >
> > > > I am looking for some advice on how to go about debugging Apache
> 1.3.33/
> > > > PHP 5.0.4 on a production Linux box (RHE 3).  The scenario is this:
> > > > Once a day we find a segfault in our apache logs.  From our current
> position,
> > > > we don't know what page was accessed, and our 400+ users haven't
> brought
> > > > the issue to our attention.  All we know is the date/time and PID of
> when
> > > > the segfault occurred.  The question is this:  how can we go about
> isolating
> > > > the offending requested page that bombs?
> > >
> > > What you could do is  set up a proxy in front of you server. Let the
> > > proxy log all requests. The request that causes the server to bomb
> > > will probably be listed with an error  message in the proxy's log,
> > > otherwise you always have the timestamps.
> > >
> > > Krist
> > >
> 
> Would adding the PID to your access_log help any?  %P in your logFormat.
> We use the following in our httpd.conf:
> 
> LogFormat "%h %l %u %{[%d/%b/%Y:%T %z]}t \"%r\" %>s %b \"%{User-Agent}i\"
> %{VHOST}e[%P]"
> icombined
> CustomLog /usr/local/apache/logs/access_log icombined
> 
> I believe the access_log entries are written at the end of the process, ie
> the seg
> fault probably happens before the access_log entry is written.  But you
> may be able
> to see where the user is headed..?
> 
> marc
> 
> 
> 
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org



CONFIDENTIALITY NOTICE
This message contains confidential information intended only for the use of
the individual or entity named as recipient. Any dissemination, distribution
or copying of this communication by anyone other than the intended recipient
is strictly prohibited. If you have received this message in error, please
immediately notify us and delete your copy. Thank you.

AVIS DE CONFIDENTIALITÉ
Les informations contenues aux présentes sont de nature privilégiée et
confidentielle. Elles ne peuvent être utilisées que par la personne ou
l'entité dont le nom paraît comme destinataire. Si le lecteur du présent
message n'est pas le destinataire prévu, il est par les présentes prié de
noter qu'il est strictement interdit de divulguer, de distribuer ou de
copier ce message. Si ce message vous a été transmis par mégarde, veuillez
nous en aviser immédiatement et supprimer votre copie. Merci.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message