{"id":258,"date":"2012-04-12T09:23:24","date_gmt":"2012-04-12T08:23:24","guid":{"rendered":"https:\/\/silicondales.com\/?p=258"},"modified":"2018-11-25T16:49:20","modified_gmt":"2018-11-25T16:49:20","slug":"apache-httpd-address-already-in-use-make_sock-could-not-bind-to-address","status":"publish","type":"post","link":"https:\/\/silicondales.com\/tutorials\/aws-ec2\/apache-httpd-address-already-in-use-make_sock-could-not-bind-to-address\/","title":{"rendered":"Apache HTTPD: Address already in use: make_sock: could not bind to address"},"content":{"rendered":"

This is a post for those sysadmins out there who run into problems running servers with a LAMP setup. This issue will crop up occasionally in AWS<\/a> Linux, on EC2 instances, but its a common error on Linux<\/a> systems running apache<\/a> as a web server.<\/p>\n

Occasionally, for some reason or another – usually because you changed some setting – it is necessary to restart apache from the terminal (i.e. in PuTTy).<\/p>\n

Sometimes, though this is rare, this fails. If apache fails to restart and displays a message similar to “Address already in use: make_sock: could not bind to address” then you may be wondering how to get your server back online!<\/p>\n

The precise message you receive could look something like this:<\/p>\n

Starting httpd: (98)Address already in use: make_sock: could not bind to address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [::]:80<\/p>\n

(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
\nno listening sockets available, shutting down
\nUnable to open logs<\/p><\/blockquote>\n

You may or may not have other error messages, but let’s deal with this one!<\/p>\n

The slow fix is to do a full hardware reboot of your server. This takes quite some time, and is not necessarily the best course of action, but it should solve this issue.<\/p>\n

The reason for the message, however, is that there are still active connections which were not closed before. Probably some process was running when you hit “restart” (you should identify just what by checking – but that’s beyond the scope of what we’re doing here!). In any case, you’ll want to find out what process is running, and “kill” it.<\/p>\n

Here’s how:<\/p>\n

1) Type “ps -aux |grep httpd<\/code>”<\/p>\n

2) This will return a set of processes which are currently running. There should not be more than one or two. It will look something like this:<\/p>\n

root\u00a0\u00a0\u00a0\u00a0 23605\u00a0 0.1\u00a0 0.1 861052 21208 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Ss\u00a0\u00a0 10:07\u00a0\u00a0 0:00 \/usr\/sbin\/httpd
\napache\u00a0\u00a0 23609\u00a0 0.0\u00a0 0.0 220500\u00a0 7720 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 S\u00a0\u00a0\u00a0 10:07\u00a0\u00a0 0:00 \/usr\/sbin\/httpd
\nroot\u00a0\u00a0\u00a0\u00a0 23697\u00a0 0.0\u00a0 0.0\u00a0 61184\u00a0\u00a0 776 pts\/0\u00a0\u00a0\u00a0 S+\u00a0\u00a0 10:10\u00a0\u00a0 0:00 grep httpd<\/p><\/blockquote>\n

3) Kill the apache processes which are showing by typing:<\/p>\n

kill -9 23609<\/p><\/blockquote>\n

Remember to replace “23609” with whatever number your process actually is!<\/p>\n

An alternative to this, if you have a lot of processes all running, is to use the “killall” method, which is:<\/p>\n

killall -9 httpd<\/code><\/p><\/blockquote>\n

Then restart apache – it should work correctly!<\/p>\n

You’ll then want to set about identifying which processes were causing this in the first place!<\/p>\n

Leave a comment below if this worked for you – or if it didn’t – and we might<\/em> be able to help.<\/p>\n","protected":false},"excerpt":{"rendered":"

This is a post for those sysadmins out there who run into problems running servers with a LAMP setup. This issue will crop up occasionally in AWS Linux, on EC2 instances, but its a common error on Linux systems running apache as a web server. Occasionally, for some reason or another – usually because you … <\/p>\n

Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[12],"tags":[82,118,817,818,996,1056],"acf":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/silicondales.com\/wp-json\/wp\/v2\/posts\/258"}],"collection":[{"href":"https:\/\/silicondales.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/silicondales.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/silicondales.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/silicondales.com\/wp-json\/wp\/v2\/comments?post=258"}],"version-history":[{"count":0,"href":"https:\/\/silicondales.com\/wp-json\/wp\/v2\/posts\/258\/revisions"}],"wp:attachment":[{"href":"https:\/\/silicondales.com\/wp-json\/wp\/v2\/media?parent=258"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/silicondales.com\/wp-json\/wp\/v2\/categories?post=258"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/silicondales.com\/wp-json\/wp\/v2\/tags?post=258"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}