On Tue, Sep 25, 2007 at 10:27:11AM -0700, Neil Schneider wrote: > There are two things that will cause Apache to not start. One is binding to an > IP address that is not configured on the host. The other is DNS that cannot > resolve the host name configured in Apache.
There's a third possible culprit... selinux Red Hat *swore* that SELinux has been greatly improved, that there are default configs for hundreds of apps, etc. Yet, several times, I've had apache refuse to start on a machine, and disabling selinux fixes it. Look in /etc/selinux/config If SELINUX= enforcing or permissive, change it to disabled and reboot, and I'll bet apache fires right up. Disabling SELinux isn't technically the "right" answer... you're supposed to fix the context for the app in question until it does work. -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * *********************************************************************** -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
