Apache restart on Ubuntu – error “could not bind to address 0.0.0.0.80”

apacheApache2Ubuntu

I'm a n00b – trying to get apache2 set up on Ubuntu 9.10 (Karmic Koala) on Rackspace Cloud. I have set up/configured OpenSSL and installed Apache, but Apache won't start. I assume its a misconfiguration in my /etc/apache2/sites-available/ssl or /etc/apache2/sites-available/default files)

When I try to restart apache using the command:

sudo /etc/init.d/apache2 restart

I get the following error message:

[error] (EAI 2)Name or service not known: Could not resolve host name *.80 — ignoring!
[error] (EAI 2)Name or service not known: Could not resolve host name *.80 — ignoring!
(98)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
…fail!

For my /etc/apache2/sites-available/ssl I have used a virtual host of *:443.

For my /etc/apache2/sites-available/default i have used a virtual host of *:80

Best Answer

Turn off Skype. It's use port number 80 for incoming messages. Eventually check what use this port at the moment using netstat.

Second resolve is simply: Add ServerName localhost to main config. file.

Related Solutions

Linux – Amazon EC2 – Apache server restart issue

I ran into this problem when I installed apache from source, but then tried to run

$ sudo /etc/init.d/httpd restart

which was using a pre-installed version of apache. The stop directive in /etc/init.d/httpd was not removing the httpd.pid file that was created when starting the source-installed version of apache.

To determine if this is also the reason for your problem, find where the httpd.pid file is getting set when you run

$ sudo apachectl start

If you installed from source and apache2 is living in /usr/local/apache2, then the httpd.pid file should get created in /usr/local/apache2/logs. When you stop apache by running

$ sudo apachectl stop

this file should get removed. So to test if the httpd.pid file is causing your problem, start apache by calling

$ sudo apachectl start

and locate the httpd.pid file. Then try stopping apache by using

$ sudo /etc/init.d/httpd stop

If the original httpd.pid file is still present, then that is why apache is unable to start when you use

$ sudo /etc/init.d/httpd start

To get my /etc/init.d/httpd file to work correctly, I explicitly put the call to apachectl in the start and stop methods:

#!/bin/bash
# /etc/init.d/httpd
#
# Path to the apachectl script, server binary, and short-form for messages. 
apachectl=/usr/local/apache2/bin/apachectl 
httpd=/usr/local/apache2/bin/httpd 
pid=/usr/local/apache2/logs/httpd.pid 
prog=httpd 
RETVAL=0

start() {
    echo -n $"Starting $prog: "
    $apachectl -k start
    RETVAL=$?
    echo
    return $RETVAL
}
stop() {
    echo -n $"Stopping $prog: "
    $apachectl -k stop
    RETVAL=$?
    echo
}

Apache – Starting apache fails (could not bind to address 0.0.0.0:80)

Worked for me running this command:

fuser -k -n tcp 80

Best Answer

Related Solutions

Linux – Amazon EC2 – Apache server restart issue

Apache – Starting apache fails (could not bind to address 0.0.0.0:80)

Related Topic