|
Home > Archive > Web Servers on Unix and Linux > February 2005 > Seg faults, but why ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Seg faults, but why ?
|
|
| ytz997@gmail.com 2005-02-08, 5:49 pm |
| my error_log is full of segment* faults, removed 400 Mb error_log file
how can i find out why do these occour ?
i modified mod_setenvif, added fprintf(log,"%d %s\n",getpid(),r->uri);
but this log doesn't pids that error_log mentions :\
| |
| Dan Wilga 2005-02-09, 5:49 pm |
| In article <1107885238.325156.8980@l41g2000cwc.googlegroups.com>,
ytz997@gmail.com wrote:
> my error_log is full of segment* faults, removed 400 Mb error_log file
>
>
> how can i find out why do these occour ?
> i modified mod_setenvif, added fprintf(log,"%d %s\n",getpid(),r->uri);
> but this log doesn't pids that error_log mentions :\
The problem is that Apache normally only generates a log entry after the
request has finished. In this case, it's segfaulting before that can
happen.
Try looking at mod_log_forensic. It can log every request before it's
processed.
--
Dan Wilga dwilga-MUNGE@mtholyoke.edu
** Remove the -MUNGE in my address to reply **
|
|
|
|
|