apache22 is not running

i started the apache22 and it says

"Syntax OK
Starting apache22"

but when i checked the status, apache22 is not running... it says
"apache22 is not running."
why is it? can somebody help me on this problem?
 
Have you looked at your error log (/var/log/httpd-error.log)? If yes, what's in there, and if no, why not?
 
i have the same problem. log error:
Code:
[Thu Jan 07 01:41:51 2010] [alert] (EAI 8)hostname nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of "nothing.com"
Configuration Failed
[Thu Jan 07 01:47:05 2010] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Jan 07 01:47:05 2010] [alert] (EAI 8)hostname nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of "nothing.com"
Configuration Failed
[Thu Jan 07 01:51:24 2010] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Jan 07 01:51:24 2010] [alert] (EAI 8)hostname nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of "nothing.com"
Configuration Failed
 
Check if the hostname is set properly. Not only in your httpd.conf but also in rc.conf. Double check to make sure name resolving works.
 
I tried running apache22 as regular(not root)user. I got this:
Code:
(13)Permission denied: make_sock: could not bind to address [::]:80
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
could this be causing the problem?
 
potobenka said:
I tried running apache22 as regular(not root)user. I got this:

cout this be causing the problem???

No this isn't causing the problem, non-root user dont have the permission to bind sockets.
 
AFAIK if you run httpd as root, it'll fall back to a user and group specified in the httpd.conf (by default it's 'nobody', I think). If you still want to run it as a non-root user, use port above 1024.
 
Either disable mod_unique_id in your httpd.conf file or make sure "nothing.com" resolves to your local machine.

I think you can get around that by putting your machine's IP address in the hostname section of your httpd.conf file.
 
Back
Top