(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443

the_ajp · 04-20-2007, 07:49 AM

killall httpd
apachectl sslstart

smiams · 07-30-2007, 12:20 PM

I shut down apache:

-> sudo /etc/init.d/apache2 stop

I could not start apache back up.

-> sudo /etc/init.d/apache2 start
-> error

I had some apache processes running that needed to be shut down:

-> ps aux | grep apache | awk '{print $2}' | sudo xargs kill -9

Then I started apache

-> sudo /etc/init.d/apache2 start
-> success

smiams · 07-30-2007, 12:21 PM

ooops, I accidentally posted the reply 3x. Wish there was a delete button.

smiams · 07-30-2007, 12:23 PM

ooops, I accidentally posted the reply 3x. Wish there was a delete button.

divide by zero · 07-31-2007, 01:16 PM

Quote:

Originally Posted by andrabr

My GUESS is Apache was already grabbing this port via a virtual host in another config file, and a second attempt to hold onto it confues good old Apache to such an extent that it would just totally give up. This could be happening to you ;-)

im having the same problem, however this is not the case. the only directive that tells apache to listen is Listen. having an ip : port in a VirtualHost directive does NOT actually make apache listen on that ip : port.

my problem is similar, only i have 2 listen directives, one for 80 and one for 443. there are no others in any conf file. on top of that, no other process is bound to port 443. this is a real WTF right here.

attilahooper · 09-23-2007, 10:47 AM

I have FC6 with the apache package and it was blowing up on port 80 'cannot bind' etc. I registered to thank Watski for posting this fix. I see that this was his only post too, good going bro'. thxthxthx

I too was confused as hell cause netstat showed no active processes using 80.

This worked beautifully:

Quote:

Originally Posted by watski

I had this problem too. It turned out that i had the "Listen 80" directive in two config files:

/etc/httpd/conf/httpd.conf
/etc/httpd/conf.d/system-config-httpd.conf

The latter comes from the Fedora Core system configurator for httpd. Removing "Listen 80" from httpd.conf solved the problem. I tried the above descriptions but I had noone listening on port 80 which got me confused.

Cheers,
Johan

optikfiberz · 10-17-2007, 10:48 PM

Quote:

Originally Posted by pushkarbhatkoti

Why this problem comes:
-------------------------------
this problem is comes only if u started the weberver and than made some modification or tried to load the jsp or asp support than u will find http locked when u tried to restart it .

so don't be confussed. just kill th process and than put ur configuration (original file) which has port 80 or 443.

it will work fine......

else mail me on my personal mail ilel
pushkar_bhatkoti@rediffmail.com
yahooo: pushkarbhatkoti@yahoo.com

My mobile is : 9810774912
I lives in New Delhi India.
cheers!!

pushkarbhatkot: thanks a lot for your post and info about lsof. Here is the shell output I got when performing the task.

Code:

box:/usr/local/apache/conf# lsof -i :80
COMMAND   PID   USER   FD   TYPE   DEVICE SIZE NODE NAME
bash    28009 apache    3u  IPv6 58865005       TCP *:www (LISTEN)
box:/usr/local/apache/conf# kill -9 28009
box:/usr/local/apache/conf# /etc/init.d/apachectl start
box:/usr/local/apache/conf#

So its all working now, thanks to your info about lsof.

The question I have is, why would a bash process be using port 80? Is it a freak of nature for apache to do that every so often or is there something more serious at work here. I just don't want to see it happen again..

Thanks.

- Alex

sneghi · 11-14-2007, 02:06 AM

hi guys,
I am new here!!!

This is due to two web servers running in the same ports(80/443)..
stop httpd if use apache web server!

It is caused due to port conflicts of the web server's!!
Try assigning different ports to different web server's..
Hope this will help!

ste101 · 03-05-2008, 07:10 AM

Quote:

Originally Posted by watski

I had this problem too. It turned out that i had the "Listen 80" directive in two config files:

/etc/httpd/conf/httpd.conf
/etc/httpd/conf.d/system-config-httpd.conf

The latter comes from the Fedora Core system configurator for httpd. Removing "Listen 80" from httpd.conf solved the problem. I tried the above descriptions but I had noone listening on port 80 which got me confused.

Cheers,
Johan

I'm running Apache on ubuntu gutsy. I had the same issue, and like watski, it was because Listen 80 was included within multiple config files. commenting it out of httpd.conf solved my issues.

cheers,
Ste.

netweblogic · 10-02-2008, 08:59 AM

Quote:

Originally Posted by watski

I had this problem too. It turned out that i had the "Listen 80" directive in two config files:

/etc/httpd/conf/httpd.conf
/etc/httpd/conf.d/system-config-httpd.conf

The latter comes from the Fedora Core system configurator for httpd. Removing "Listen 80" from httpd.conf solved the problem. I tried the above descriptions but I had noone listening on port 80 which got me confused.

Cheers,
Johan

Yep that worked for me too Johan!

It's a shame that instead of seeing your post, I went over each step of the first posts, then figured it out when I changed the httpd.conf file to listen to port 88.

javahaxxor · 01-23-2009, 09:48 AM

Quote:

Originally Posted by divide by zero

im having the same problem, however this is not the case. the only directive that tells apache to listen is Listen. having an ip : port in a VirtualHost directive does NOT actually make apache listen on that ip : port.

my problem is similar, only i have 2 listen directives, one for 80 and one for 443. there are no others in any conf file. on top of that, no other process is bound to port 443. this is a real WTF right here.

Check for similar Listen directives in other httpd.conf files (updatedb;locate httpd.conf)
That was my problem, I had to comment out the last two:
Listen soleshop.x.com:80
Listen soleshop.x.com:443
Listen soleshop.x.com:8000
Listen soleshop.x.com:8002
Listen soleshop.x.com:8004
Listen soleshop.x.com:8006
Listen soleshop.x.com:8007
#Listen ebusiness.x.com:80
#Listen ebusiness.x.com:443

I guess that this can be "fixed" by saying:
Listen *:80
Listen *:443
Listen soleshop.x.com:8000
Listen soleshop.x.com:8002
Listen soleshop.x.com:8004
Listen soleshop.x.com:8006
Listen soleshop.x.com:8007
#Listen ebusiness.x.com:80
#Listen ebusiness.x.com:443

boogiebogdy · 05-25-2009, 08:33 AM

Hey,

I know this topic is a little bit old, but i'll try my chance.
The server was working fine, the load was small, uptime a few weeks, and in a minute every died, only the ping and ssh remained alive.
I have received this error
"(98)Address already in use: make_sock: could not bind to address [::]:443" so i stopped httpd and i have looked to see who was listening on port 443. It was sshd. I really don't have any ideas how that was possible.

I didn't had any choice and i had to reboot the server. Now everything is fine, but i don't want things like this to happend in the future. Any idea somebody?

stryker_oz · 07-04-2009, 11:57 PM

Quote:

Originally Posted by watski

I had this problem too. It turned out that i had the "Listen 80" directive in two config files:

/etc/httpd/conf/httpd.conf
/etc/httpd/conf.d/system-config-httpd.conf

The latter comes from the Fedora Core system configurator for httpd. Removing "Listen 80" from httpd.conf solved the problem. I tried the above descriptions but I had noone listening on port 80 which got me confused.

Cheers,
Johan

Johan, thankyou. Just installed FC11 with apache and this was precisely the issue I had. That was far from an obvious resolution - apache was in fact clashing with itself after all.

sreejithedl · 10-12-2009, 10:58 AM

I found the solution here. Its perfect.

<<advertising link removed>>

buffe · 03-30-2010, 06:36 AM

Hi,
I have applied some configurations to my httpd.conf file and restarted the server and the following error has come,

Starting httpd: [Tue Mar 30 16:13:40 2010] [warn] module php5_module is already loaded, skipping
(98)Address already in use: make_sock: could not bind to address [::]:443
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs

the configurations I have added are as follows,

JkWorkersFile /usr/local/tomcat/conf/workers.properties
JkLogFile /etc/httpd/logs/mod_jk.log
JkLogLevel info
JkLogStampFormat "[%a %b %d %H:%M:%S %Y]"

<VirtualHost _default_:443>
SSLEngine on
SSLCertificateFile /etc/httpd/conf/ssl.crt/app_name.crt
SSLCertificateKeyFile /etc/httpd/conf/ssl.key/app_name.key
JkMount /app_name* ajp13

</VirtualHost>

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

I couldn't figure out the problem. It would be nice If some one can help me with this.

Thank you