up vote 1 down vote favorite
share [g+] share [fb]

we just got through a power outage. All our servers came back up properly, except out web server gives me this error when attempting to start apache:

# apachectl start
no listening sockets available, shutting down
Unable to open logs

I've verified that there are no processes using the port apache is configured to listen on, and I can't fine apache running in ps aux. Does anyone have any suggestions for troubleshooting this?

link|improve this question
57% accept rate
feedback

4 Answers

up vote 0 down vote

127.0.0.1 DNS servers, can you check in your /etc/hosts 127.0.0.1 then try to start the services

link|improve this answer
I'm not sure what you're asking, but the line in /etc/hosts that starts with 127.0.0.1 is '127.0.0.1 localhost localhost.my.domain' – JohnB Sep 20 '10 at 18:57
I should note that this server has been running without issue for several years, and nothing has changed on it for the past couple months. – JohnB Sep 20 '10 at 19:03
i m asking do you have 127.0.0.1 entry at hosts file or yours DNS entry suppose if you have config johnb.com that is redirected to 127.0.0.1 – Rajat Sep 20 '10 at 19:04
but right now its not work you said – Rajat Sep 20 '10 at 19:04
no, I just have the 127.0.0.1 entry in /etc/hosts the way I wrote it in my first comment. – JohnB Sep 20 '10 at 19:13
show 1 more comment
feedback
up vote 0 down vote

Is anything else listening on port 80? netstat -nlt show anything else on 80?

Has servername changed and/or resolv.conf not able to do a reverse lookup on starting up apache.

Does hostname -f resolve properly?

link|improve this answer
feedback
up vote 0 down vote

Apache won't start if it can't log. The second line, Unable to open logs, jumps out at me more so than the first.

Check to make sure that there's enough disk space for the path which you are logging.

df -H

Also, verify permissions for the logging directory and files.

ls -al /var/log/httpd

link|improve this answer
feedback
up vote 0 down vote accepted

Ok, I figured out the problem - sorry the answer is so late in coming, things are really busy here. Thanks for all your help!

The problem was that this server has a special setup, and I needed to pass apachectl the -d SSL option for it to start.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.