The EEP of the second instances refuses to start

Document ID : KB000086740
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
EEP log:
Could not add listen endpoint on 0.0.0.0:XXXXX. Could not bind socket (errno=67)

Patch level detected:Dollar Universe 6.3.01
Product Version: Dollar.Universe 6.3.01

Description :After an upgrade of the second DUAS instance on a system with multiple instances and multiple Network Interface Cards:

- The EEP of the second instances refuses to come up at startup with following error in the logs.
- Netstat reveals that the EEP port is actually taken by on specific IP by the EEP of the already running instance.
Environment:
OS: All Unix
Cause:
Cause type:
Configuration
Root Cause: This is a setting issue. Following variables have to be created in the environment with the correct settings.
U_CLUSTER and UNI_SRV_BIND_NAME 
U_CLUSTER set to Y allows the processes to bind the IP or related NIC that ressolves the node name U_LOCALHOSTNAME.
UNI_SRV_BIND_NAME forces EEP must be set to the Hostname set in U_LOCALHOSTNAME.
Resolution:
Stop the node
Check that all the Dollar Universe process are correctly stopped
Execute the following command from the bin folder

./unisetvar U_CLUSTER Y
./unisetvar UNI_SRV_BIND_NAME 

Restart Dollar Universe (DUAS should be restarted because both settings are static).

Fix Status: No Fix

Additional Information:
Workaround :
N/A