Re: [suse-linux-uk-schools] Installing Apache
![](https://seccdn.libravatar.org/avatar/90b9853978fbf5a1812de83ad235ef95.jpg?s=120&d=mm&r=g)
[crit] (98)Address already in use: make_sock: could not bind to port 80
This means that something else is already listening to the TCP port that a web server would normally use - so, are you already running apache (or even another web server) on the box ? If you do # netstat -na | more This will list all currently running (and listening) network servers. Look for something like the following : tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN If you see this you are certainly running a program already listening to port 80. If you try # ps -aux | more you can look for something that could be a web server (apache is always listed as httpd). If it is not this, then the only other thing I can think of, is - is it possible you are trying to start apache twice - ie the first one starts, but the second one gives the error ? As a test, you could try specifing another port (is this in httpd.conf or it may be a command line option) eg 8080 and see if it starts up ok on this port (you would have to connect to the URL http://you.machine:8080/ in order to view its home page though). Hope this helps, Kevin.
![](https://seccdn.libravatar.org/avatar/a16bb5b2f1f0a63c9ffe1dff1ccc521c.jpg?s=120&d=mm&r=g)
Hi, kevin.taylor@powerconv.alstom.com wrote:
[crit] (98)Address already in use: make_sock: could not bind to port 80
This means that something else is already listening to the TCP port that a web server would normally use - so, are you already running apache (or even another web server) on the box ?
< snip Kevin's excellent advice > Also try: telnet localhost 80 type in a randon string, press return a couple of times, see what comes back at you. If that's no help then "lsof" seems to be the package of choice for finding out what process is listening on which port, but I suspect telnetting to local port 80 will reveal some helpful info. -- I wish outer space guys would conquer the Earth and make people their pets, because I'd like to have one of those little beds with my name on it.
![](https://seccdn.libravatar.org/avatar/18d9dd9bb983e18914064c243cb36db9.jpg?s=120&d=mm&r=g)
Also try:
telnet localhost 80
type in a randon string, press return a couple of times, see what comes back at you.
If that's no help then "lsof" seems to be the package of choice for finding out what process is listening on which port, but I suspect telnetting to local port 80 will reveal some helpful info.
You could also try 'fuser -n tcp 80' run as root. Which will list the process ids of anything using port 80.
participants (3)
-
kevin.taylor@powerconv.alstom.com
-
Mark Evans
-
Nick Drage