Let's say the following is in the HPEL or SystemOut log. This error occurs when attempting to start a WebSphere application server. In this example, the unknown host name is "server1".
WSVR0009E: Error occurred during startup
com.ibm.ws.exception.RuntimeError: org.omg.CORBA.INTERNAL:
defaultLocalHost:java.net.UnknownHostException: server1: server1: unknown error vmcid: IBM minor code: 583 completed: No.
If "server1" is not the fully qualified domain name, this suggests that the hostname of the Linux server is "server1" instead of the fully qualified domain name. For example, if the fully qualified domain name is server1.example.com, update the /etc/hostname file to have server1.example.com as the hostname. Try to start the application server after and updating the hostname.
echo "server1.example.com" > /etc/hostname
Ensure that the hostname (server1 in this example) can be resolved to an IP address. If the hostname cannot be resolved to an IP address, DNS will need to be configured to resolve the hostname to an IP address. In this example, the nslookup command confirms that hostname server1 does not resolve to an IP address.
nslookup server1
Server: 10.1.2.3
Address: 10.1.2.3:53
** server can't find was1: NXDOMAIN
After confirming the DNS server to resolve was1 to an IP address, the server should be able to be started. In this example, the nslookup command confirms that hostname server1 resolves to IP address 10.14.55.201.
nslookup server1
Server: 10.1.2.3
Address: 10.1.2.3:53
Name: server1
Address: 10.14.55.201
Did you find this article helpful?
If so, consider buying me a coffee over at