[OTD-10380] Error creating socket (Address not available)-startup failure: could not bind to xx.xx.xx.xx:7001 (Cannot assign requested address) in active-passive fail-over (Doc ID 2269485.1)

Last updated on MAY 23, 2017

Applies to:

Oracle Traffic Director - Version 11.1.1.7.0 to 11.1.1.9.0 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

During active-passive fail-over configuration, the following Errors are reported:

[ERROR:32] startup failure: could not bind to xx.xx.xx.xx:7001 (Cannot assign requested address)
[ERROR:32] [OTD-10380] uatidm: http://xx.xx.xx.xx:7001: Error creating socket (Address not available)

Changes

It's active-passive setup. Imagine, the OTD crashes on the first node, the second one would need to bring up the listeners on the same IPs that were used on the first node. However, since this IP will still be on the network as it's beyond OTD control that would lead to duplicate IPs on the same network.

The UAT node is listening Not on OTD VIP but on it's own physical IP. This is how the setup is configured.

However, failover won't work anyway since the listeners are bound to the physical IP of another node.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms