Reset Search
 

 

Article

4404 - "Failed to bind to any local address" error when IP address is specified manually on the vTM

« Go Back

Information

 
Last Modified Date6/6/2018 9:36 AM
Synopsis

When hosting any critical services, it is generally recommended to use a traffic IP group across multiple traffic managers to ensure high availability. For certain services, some customers may choose to manually specify an IP address to listen on. When it is not configured correctly, you may see an error like this:

Failed to bind to any local address

Problem or Goal
Cause
Solution

You can manual specify an IP address to listen on by going to Services > Virtual Servers > {VS-name} > Basic Settings within Domain names and Local IP addresses ... under Listening on. For instance, if you have a cluster of two vTMs load balancing traffic against a pool of web servers. TM1 has a local IP address 192.168.56.101 and TM2 has 192.168.56.102. If you specify 192.168.56.101 for the relevant Virtual Server, you will see this error in Event Log:

12/Oct/2012:22:33:28 +1100 SERIOUS Virtual Server webserver: Failed to bind to any local address tm-2

Since IP address 192.168.56.101 is only local to TM1, this error is correctly thrown by TM2. Within the /logs/errors file of TM2, you should see the following entry:

[12/Oct/2012:22:33:28 +1100] SERIOUS vservers/webserver vs_bindlocal_fail Failed to bind to any local address

However, please note that even with this error, the VS should be still listening on TM1, which you could verify using netstat:

tm-1:/opt/zeus/log# netstat -pan | grep LISTEN | grep ":80 "
tcp 0 0 192.168.56.101:80 0.0.0.0:* LISTEN 2681/zeus.zxtm


To overcome this error completely, you need to specify an IP address for all the TMs in the cluster. For this example, we should instead specify the followings for the VS Domain names and IP addresses:

192.168.56.101 192.168.56.102

There should not be any further bind errors. And using the same netstat test, you could verify as follows:

root@tm-1:~# netstat -pan | grep LISTEN | grep ":80 "
tcp 0 0 192.168.56.101:80 0.0.0.0:* LISTEN 2681/zeus.zxtm

root@tm-2:~# netstat -pan | grep LISTEN | grep ":80 "
tcp 0 0 192.168.56.102:80 0.0.0.0:* LISTEN 2659/zeus.zxtm

Related Links
Attachment 1 
Created ByVenkataKondaReddy Palem

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255