From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
'/etc/rc.d/init.d/httpd start' or '/usr/sbin/httpd' both appear to complete
successfully (in the former case, it lists 'OK', and in the latter, a command
prompt is returned - in both cases syslog shows 'httpd startup succeeded'),
however, the process only lives for a few ticks, and then dies an abrupt death.
I produced a minimal httpd.conf to reproduce this problem:
LoadModule perl_module modules/mod_perl.so
LoadModule php4_module modules/libphp4.so
LoadModule ssl_module modules/mod_ssl.so
If any of the LoadModule lines are commented out, the problem
disappears. All three seem to need to be present in order for me
to reproduce my difficulty. The strace output for a sample failure
can be found at:
From the strace output, it looks like /usr/lib/php4/snmp.so is
doing something improper. There is another ticket that describes
similar behaviour to mine in bugzilla that refers to issues with
php4/snmp.so but is not specific enough, and describes different
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Execute /usr/sbin/httpd using the config file from the
httpd dies with sigsegv shortly after it successfully starts.
httpd should live.
OK, and if you remove the php-snmp package does this go away?
After removing php-snmp using 'rpm -ev', I am unable to reproduce the problem
with the httpd.conf from the Description text.
So it looks as if I am experiencing the same problem as the other ticket,
although in my case, httpd continued to crash when I booted up with
linux-2.4.21. (The other person experiencing this or a similar problem
claimed that the problem only appeared when using the beta1 kernel)
I had this same problem... checking the ssl_error_log showed that the ssl
certificate that is installed by default is for hostname=localhost.localdomain,
and when i installed severn, i chose a different hostname for my machine.
What worked for me was to rename /etc/httpd/conf.d/ssl.conf to ssl.orig (to
avoid having ssl loaded) after that it worked again!
*** This bug has been marked as a duplicate of 97207 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.