can't start Apache on Mac OS X--no listening sockets available?

[7stud]

> On Jun 25, 7:23 pm, 7stud <bbxx789_0... at yahoo.com> wrote:
>
>
>
> > I'm trying to get Apache set up on my system so I can use mod_python.
> > I installed Apache 2.2.4 according to the following instructions:
>
> >http://switch.richard5.net/isp-in-a-box-v2/installing-apache-on-mac-o...
>
> > and everything seemed to install correctly, but I can't start Apache.
> > I typed in the following command:
>
> > $ sudo /Library/Apache2/bin/apachectl start
> > Password:
>
> > and I got this error message:
>
> > httpd: Could not reliably determine the server's fully qualified
> > domain name, using tms-computer.local for ServerName
> > (48)Address already in use: make_sock: could not bind to address
> > 0.0.0.0:80
> > no listening sockets available, shutting down
> > Unable to open logs
>
> > Any ideas?
>
> Do you have "Web Sharing" in the prefs on as well?  

I checked and to my surprise Personal Web Sharing was turned on.  I
was messing around with it yesterday because I thought that might have
something to do with my problems, but I couldn't get Personal Web
Sharing to start--it just said "Web Sharing starting up...", and it
never did.

Anyway, I turned Personal Web Sharing off, and then the error message
changed to this:

$ sudo /Library/Apache2/bin/apachectl start
Password:
httpd: Could not reliably determine the server's fully qualified
domain name, using tms-computer.local for ServerName

However, I checked the All Processes page in the Activity Monitor, and
it said httpd was running.  So I tested my apache installation by
typing http:/localhost in Safari's address bar, and a page displayed
saying "It works!".  But I wondered if that page was being served up
by the pre-installed version of Apache or my new installation.  So, I
went into my new installation's directory and looked at the file:

/Library/Apache2/htdocs/index.html

and changed the text from "It works!" to "Apache 2.2.4", but when I
retyped http:/localhost in Safari's address bar, I still got a page
saying "It works!", so that page is not being served by my new
installation.