05Jan2008
Address already in use: make_sock: could not bind to address – Apache – HTTPD Error
I was getting the following error on one my servers, after updating apache2 and php5
Starting web server (apache2)...(98)Address already in use: make_sock: could not bind to address [::]:80 (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 failed!
This is what I did to fix the problem
netstat -lnp | grep '80'#output tcp6 0 0 :::80 :::* LISTEN 18712/apache2
In my case the output showed that apache2 was already using the port, although no sites was working and it was not even possible to stop the apache2 daemon. I ran the following to learn more
ps 18712 PID TTY STAT TIME COMMAND 18712 ? Ss 0:00 /usr/sbin/apache2 -k start
I killed the apache2 process, which was blocking everything
kill 19712
and restarted apache
/etc/init.d/apache start
and everything was working fine again. Hopefully this is useful for someone..
Very useful, thank you very much!
Wow!
I was sweating bullets with my server down after a misconfiguration!
This helped me get back online! … and I can go to bed now…
Thanks!
FINALLY, an answer to my problems. Thanks!
YESS,
your help save my life
than you!
Thank you so very much. Saved my week end
wouah thanks a lot, by taping the message in google i got 1 page of bad tips and fucking spams until i find you
Yup that’s some useful piece of information.
thanks, very helpful
This has fixed the problem, but how can we make sure that it never happens again. cause we have some good spec server and whenever this happens every few hours, when we check, we notice that the server memory and cpu are running fine and have not been fully consumed. nevertheless, this problem would put the port 80 to a halt and would stop users from browsing our site as a result since no network/traffic gets in to our server.
Thanks.
Danham
thank you ,is the answer to the question!
i like you
just what the doctor ordered.
My case was that the SSL passphrase was not entered upon boot of the server and the start-up continued anyway.
I guess that the lack of authentication had something to do with the symptoms.
Thanks, this worked great!
Thank you so much!
It really works.
I wish I would have found this post about 8 hours ago.:) Problem is that does not fix my problem. If I reboot, then problem reappears. This all happened when I did the initial install on my test network, and then moved the server to my production network. Does this have anything to do with SSL and the subnet it was on when configured?
thanks so much for your answer
br
Your post really helped me, thanks.
My case is quite similar, except the result of netstat -tulpn| grep :80 is:
tcp 0 0 173.45.110.168:80 0.0.0.0:* LISTEN –
No process name/id! Any ideas?
Thanks you so much for helping me..
Good Golly. Thank you for this!