Odd Apache 1.3 init script problem after kernel upgrade

[whit]

Rebooted a system with a 2.6.0-test11-gentoo-r2 kernel that had been running 2.4.23. Apache 1.3 didn't start normally from the /etc/init.d script in the default runlevel. Trying to run the init script manually gave an error that apache was already running. Running the init script with "zap" and then "start" again still failed to start it. Nothing notable was in the apache or system logs - just ended up with no apache daemon running.

Well, "apachectl start" worked fine. And after doing that the init script seems to be working okay again. Don't know what it could have been about a reboot for a kernel upgrade (after a normal shutdown) that would confuse Gentoo's apache init script. Just leaving this note here in case someone else runs into the same oddness.

Also, I've switched my monit config to use apachectl instead of the Gentoo apache init, since it's apparently more robust.

[ckdake]

most likely it left a pid file in /var/run that got everyhing confused. Also, if i remember correctly there is an init.d/running/ folder somewhere. When I was getting bind working it would put an entry in that folder and if something bad happened to bind (which it did a lot ), I would have to delete that file to get the init.d script to start it up again.
_________________
http://ckdake.com/