What's on port 80?

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: sinck@ugive.comsinckugive.com
Date:  
Subject: What's on port 80?

\_ Ok Debian fans, I've got a strange situation here.
\_ 
\_ My Apache isn't starting up.  The contents of the error.log say:
\_ 
\_ >cat /var/log/apache/error.log
\_ [Wed Dec 27 20:11:32 2000] [crit] (98)Address already in use: make_sock: could
\_ not bind to port 80
\_ [Wed Dec 27 21:46:53 2000] [crit] (98)Address already in use: make_sock: could
\_ not bind to port 80
\_ [Wed Dec 27 22:12:49 2000] [crit] (98)Address already in use: make_sock: could
\_ not bind to port 80
\_ [Wed Dec 27 22:13:34 2000] [crit] (98)Address already in use: make_sock: could
\_ not bind to port 80
\_ >netstat -atp | grep www
\_ (Not all processes could be identified, non-owned process info
\_  will not be shown, you would have to be root to see it all.)
\_ tcp        0      0 *:www                   *:*                     LISTEN
\_ 339/dhttpd
\_ >
\_ 
\_ Anybody know what might be the problem here?


Kinda looks like something named 'dhttpd' is running and listening on
port 80, no?

try a quick 'ps -aux' and 'locate dhttpd' and see if it leaks juicy
bits.

Also consult your rc directories for amusing startups.

David