Similar situation to what both John Lamb and Sourian reported but alas
this is in a production environment. Basically I NEED php to be working
like a rock so going to Apache2 at this point in time is not really an
option.
Clean basic install of apache
When I goto boot, apache does not start as a part of the boot process.
At the moment, all of the firewall stuff has been deleted from the
machine just to ensure that this is not causing a problem (I usually use
shorewall so that is ok.)
chkconfig apache after a fresh boot says "apache on"
rcapache status though gives a "unused"
and trying to view the machine via any mechanism (either localhost, or
by domain name or by ip) gives a "could not connect" error.
In other words, apache is not running.
Do a rcapache restart and it starts up with no problems then proceeds to
work fairly ok (I'm still working the virtual servers, lets get it
finding the main before I start on those>)
messages in the error.log under httpd are
[Sun May 4 18:46:26 2003] [notice] caught SIGTERM, shutting down
[Sun May 4 19:08:01 2003] [notice] Apache/1.3.27 (Linux/SuSE) PHP/4.3.1
mod_perl/1.27 configured -- resuming normal operations
[Sun May 4 19:08:01 2003] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec)
[Sun May 4 19:08:01 2003] [notice] Accept mutex: sysvsem (Default:
sysvsem)
--
Roy Cabaniss