addNode.sh command fails with ADMU0111E error
 Technote (troubleshooting)
 
This document applies only to the following language version(s):
English
 
Problem(Abstract)
addNode.sh command fails with ADMU0111E error if multiple ipaddresses for localhost defined in hosts file.
 
Cause
Incorrect configuration in etc/hosts file
 
Resolving the problem

Following error is logged in addNode.log. HostA was used as host name when Deployment Manager and Base node was installed.


ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminException:
ADMU0036E: The Deployment Manager cannot look-up by name host HostB at address
192.168.1.100
at
com.ibm.ws.management.tools.NodeFederationUtility.throwExceptionIfCellMgrCannotPing
(NodeFederationUtility.java:1625)

Here is the etc/hosts file before correcting the bad configuration.

192.168.1.100 HostA HostA.domain.com HostB
192.168.1.101 HostB HostC

There is ambiguity for HostB and ipaddress.

Modify the etc/hosts file as follows to eliminate the ambiguity.

192.168.1.100 HostA HostA.domain.com HostC
192.168.1.101 HostB

Suggested to change the hostname in deployment manager and server1 serverindex.xml to HostC then run addNode.sh command and use HostC as hostname.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Solaris
Software version: 6.0.2
Software edition:
Reference #: 1220372
IBM Group: Software Group
Modified date: Oct 20, 2005