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? With a little luck, you can get apache to leave you a core file that can later be loaded in gdb to find the problem. See: http://httpd.apache.org/docs-2.0/mod/mpm_common.html#coredumpdirectory Another alternative is mod_log_forensic: http://httpd.apache.org/docs-2.0/mod/mod_log_forensic.html which is designed to isolate requests that cause a crash. Joshua. --------------------------------------------------------------------- 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
|