Apache won't start

jhwilliams · 11-06-2007, 09:26 AM

Code:

[root@boxboro ~]# apachectl configtest
Syntax OK
[root@boxboro ~]# service httpd restart
Stopping httpd: [FAILED]
Starting httpd: [FAILED]
[root@boxboro ~]# ps aux | grep httpd | grep -v grep
[root@boxboro ~]#

It was running fine on port 80. I wanted to move it to port 8000. i changed iptables and httpd to those values, and restarted iptables service OK. upon restarting httpd, that's the message i get.

What's wrong?

soonblue · 11-06-2007, 10:19 AM

It's possible that you have conflicting listening ports in your httpd.conf file. Please post this plus your Apache error log, usually located at /var/log/httpd/error_log

Thanks!

jhwilliams · 11-06-2007, 11:28 AM

The only line mentioning a port in question is:

Code:

[root@boxboro httpd]# grep "80" conf*/*.conf | egrep -v ".*conf:#.*"
conf/httpd.conf:Listen 8000

My /var/log/httpd/error_log is not catching errors from my restart attempts. Anytime I try to restart the apache deamon, nothing new is put in the log.

I can't even start httpd manually:

Code:

[root@boxboro httpd]# httpd -e DEBUG
[root@boxboro httpd]# ps aux | grep httpd | grep -v grep
[root@boxboro httpd]#

I'll save you my httpd.conf file, nothing in it is non-standard at the moment.

soonblue · 11-07-2007, 12:22 AM

You've probably tried this already but it's just something else to try. I'll have more for you tomorrow.

Try starting the Apache service using apachectl start

jhwilliams · 11-07-2007, 09:20 PM

I have indeed tried that, I'm afraid. No luck.

I just removed httpd.conf, and reinstalled apache. The problem still persists. What now?

Thanks!

complich8 · 11-08-2007, 12:01 AM

one of the problems I've seen that prevents apache from starting and from logging meaningfully is when the log directory or logfiles aren't actually writable by the apache user. If they are, it should at least give a message in the error_log when you try to start or stop apache.

So that's my suggestion. Check the permissions on your logdir and logfiles and make sure the partition the logs are being written to isn't mounted read-only or otherwise rendered unwritable (eg: full). Also make sure that it can write its pidfile somewhere.