Gerard wrote:
> I continue to see varying amounts of chatter in the 'httpd-error.log'
> file. This is a snipped of what is being written to the file.
>
>
> **
>
> [Wed Sep 03 06:59:31 2008] [notice] Digest: generating secret for digest
> [authentication ... Wed Sep 03 06:59:31 2008] [notice] Digest: done
> [Wed Sep 03 06:59:32 2008] [notice] Apache/2.2.9 (FreeBSD) mod_ssl/2.2.9
> [OpenSSL/0.9.7e-p1 DAV/2 PHP/5.2.6 with Suhosin-Patch configured --
> [resuming normal operations Wed Sep 03 08:28:11 2008] [notice] child pid
> [1039 exit signal Segmentation fault (11) Wed Sep 03 08:56:01 2008]
> [[notice] child pid 989 exit signal Segmentation fault (11) Wed Sep 03
> [09:29:00 2008] [notice] child pid 1692 exit signal Segmentation fault
> [(11) Wed Sep 03 09:29:31 2008] [notice] child pid 990 exit signal
> [Segmentation fault (11)
>
>
> **
>
> Some days there may be twenty or more 'segmentation fault' messages. How
> can I debug this to see what is crashing and why? Everything appears to
> be operating correctly.
>
>
Easiest thing to try quickly as a stab in the dark is to comment out
extension=hash.so in your extensions.ini and restart apache. I and others
have had trouble with this one. However, when this particular problem
surfaced for me Apache wouldn't start at all, so maybe you're seeing
something else. This is just a quick "rule out a possible", but deeper
investigation is probably warranted in your case.
If this doesn't make any difference you can crank up the logging levels in
both the Apache config and the php.ini both. Instructions are in the
commented out sections of the relevant files. Careful here especially with
the php.ini as you don't want the output showing to surfers.
Sometimes truss can be a potentially helpful utility. The -f switch will
allow it to look at child processes as they fork. truss -f -p [The "root"
Apache PID]
-Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"