This can occur when an active VPN connection interferes with IP address lookup for the hostanme reported by the operating system (Windows, Linux, or MacOS) or lookup for 'localhost' due to having multiple virtual network interfaces.
The error suggests one possible solution:
- On Linux and MacOS, the hosts file is in found in directory /etc.
- On Windows, the hosts file is found in directory C:\Windows\System32\drivers\etc.
Edit the OS's hosts file to include as the first active configuration line (change the hostnames as appropriate):
127.0.0.1 localhost simpleHostName qualifiedHostName.company.com
Another solution is to
disable transient network interfaces such as VPN and WiFi.
Finally you may
bind the node at install time to a specific network interface by IP address using command options:
epadmin install node adminport=N adminhost=N.N.N.N
This explicitly binds the discovery service port to a specific port on a specific IP address. This is normally used for Proxy Discovery when UDP Multicast is made unavailable by IT network policy. The default 'adminhost' IP address is blank, binding the listener to all available interfaces (which produces a list of potential hostnames leading to the lookup problem).. Bind the node to the IP address corresponding to the hostname reported by the OS (you may need to try each IP address until you find the one that avoids the error).