> > -----Original Message-----
> > From: Krist van Besien [mailto:krist.vanbesien@xxxxxxxxx]
> > Sent: Tuesday, June 21, 2005 8:22 AM
> >
> > > On 6/21/05, Michael Caplan <michael.caplan@xxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|