Pages

Wednesday, October 3, 2012

(98)Address already in use: make_sock: could not bind to address 192.168.1.1:443 no listening sockets available


Solution for (98)Address already in use: make_sock error


The error

(98)Address already in use: make_sock: could not bind to address 192.16.1.1:443 no listening sockets available

is commonly seen when we are starting a network related service such as Apache(httpd), DNS(bind) squid etc.

When and Why this error occurs?

This error occurs when service tried to bind that particular port to the IP address. In other words for example there is service ABC running on port 443 and you tried to start some other service XYZ on the same port with out knowing that ABC service is running on that 443 port.

Technical details?

When ever you want to run a network related service we have to bind this service to a port and IP address so that once its assigned what ever packets coordinated to that service are routed through this port.

What about Solution?


Step1: First you have to check what service is running on that IP address by using nmap port mapping tool.

From the above error I am taking my IP as 192.168.1.1

nmap 192.168.1.1

Sample output



root@linuxnix.com:/var/log# nmap localhost

Starting Nmap 5.21 ( http://nmap.org ) at 2012-10-03 12:35 IST
Nmap scan report for 192.168.1.1
Host is up (0.0000090s latency).
Not shown: 997 closed ports
PORT     STATE SERVICE
53/tcp   open  domain
443/tcp  open  sshd
3689/tcp open  rendezvous

Nmap done: 1 IP address (1 host up) scanned in 0.25 seconds

Step2: Once you find the service name which occupies the port try to stop if the service is not required.

service sshd stop

Step3: Now start your Apache service and this error will vanish.




0 comments:

Post a Comment