I am trying to set up apache, and everytime that I run it, I get

linux:/usr/www/APACHE3/site.toddle # httpd -d /usr/www/APACHE3/site.toddle
no listening sockets available, shutting down
Unable to open logs

Does anyone know what this means? Thanks

There must be something already running that is listening on the ports Apache wants. Look in httpd.conf and see which port(s) you have Apache configured to listen on and run "netstat -a | more" and see if those ports are already in use.

WIth regard to the log files, check httpd.conf to see where you have Apache logging and make sure the permissions on the logging directory permit writing by the userid Apache is setup to run under, which is also in httpd.conf.

Peace...

When you type that command, how do you tell what port something is listening on? I want to use port 80, but I don't see that number on the output.

The output will look like this:

Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:6000 *:* LISTEN

but formatted well. See the "*:6000"? That is in the "local address" column. The number AFTER the colon is the port some application is listening on. So, in your output look for ":80" or ":http" or whatever port you have listed in httpd.conf. If it's the default of "8080", look for a ":8080" in the netstat output.

Here is a thread I found on the Apache mailing list that might also be of help:

http://mail-archives.apache.org/mod_...EPTUNE_MAIL%3e

Google helped me find that but a more thorough search of the Apache mailing list archives and Apache doc might provide better info for you.

Peace....

I think that I found the problem This is a line on my netstat output.

tcp 0 0 *:www-http *:* LISTEN

How do I close that service? I don't see a PID. Thanks again

Ok, that means something else is running that is binding to the same port you want Apache to bind to. Use "ps ax | more" to see what is running that might look like a candidate.

Someone else might have a better suggestion for identifying which daemon or process might be grabbing that port. Also, see if you have "inetd" or "xinetd" running. That's the "Internet Super Server" and might have grabbed port 80 to fire up a some app "on demand".

Peace...

Thanks all. I had to add
Listen 80
to my config file. I think this is only required in v.2 of Apache.