Hello,
I have a mod_perl/apache binary and configuration file that I've been using
successfully since October of last year.
Last week I ran out of disk space (and might possibly have had the server
flake out over the CPU overheating). Everything appears to be running
smoothly now with a larger fan and more disk space, except the original
httpd binary and config file I had refuse to start - it simply exits
without any error messages or log entries and without daemonizing and
spawning the necessary httpd children. httpd does not show up in the
process list at all.
I've tried to recompile httpd, but I keep getting segfaults when I try to
use any mod_perl programs, and I was hoping that instead of troubleshooting
a new compilation that perhaps it might be easier to resolve the
once-working one.
Are there any kinds of tracing tools or debugging tools that might help me
figure out why the old httpd suddenly is having problems?
--James
