The server start up for WebSphere Process Server (WPS) fails with a WSVR0009E error and a "Cannot get canonical host name for server" message
Problem(Abstract)
You cannot start the server due to problems resolving the host name.
Symptom
When this problem occurs, the following information is written to the
SystemOut.log file after you try to start the server:
0000000a WsServerImpl E WSVR0009E: Error occurred during startup
META-INF/ws-server-components.xml
[3/15/11 9:16:28:750 CST] 0000000a WsServerImpl E WSVR0009E: Error
occurred during startup
com.ibm.ws.exception.ConfigurationError:
com.ibm.ws.exception.ConfigurationError:
javax.naming.ConfigurationException: Cannot get canonical host name
for server.
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:185)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:140)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:461)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:183)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:90)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:72)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:329)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:92)
Caused by: com.ibm.ws.exception.ConfigurationError:
javax.naming.ConfigurationException: Cannot get canonical host name
for server.
at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:269)
at com.ibm.ws.security.core.SecurityComponentImpl.initialize(SecurityComponentImpl.java:90)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:1338)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:1136)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:356)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:178)
... 24 more
Caused by: javax.naming.ConfigurationException: Cannot get canonical
host name for server.
at com.ibm.ws.security.core.SecurityConfig.getHostName(SecurityConfig.java:2875)
at com.ibm.ws.security.core.SecurityConfig.setValues(SecurityConfig.java:1247)
at com.ibm.ws.security.core.distSecurityComponentImpl.initializeSecurityConfig(distSecurityComponentImpl.java:816)
at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:247)
... 29 more
Cause
This problem occurs when the server is unable to look up the host name
that was used to create the profile.
Resolving the problem
To resolve this issue, complete the following actions:
* Determine the host name used for the server by looking in the
profile_root/config/cells/cell_name/nodes/node_name/serverindex.xml
file and then work with your network or operating system administrator
to correct the problem. Check the following network settings and
report the results to your system administrator.
* Check your system manuals or man page for the availability or
equivalent commands if you find any errors in execution or the
commands in the examples below. One example, you might find the ping
command with the "command not found" error and can correct by
proceeding the command with the fully qualified path,
"/usr/sbin/ping".
*
o Start a UNIX shell and change your working directory to
/etc to execute the commands in the following example. Your system
might also place the network configuration files with other names in
different locations. The example given is from AIX 6.1
cd /etc
o Use the hostname command to report the host name for the
system. In the following example, the host name is returned as
z196p7de.
hostname
z196p7de
o Use nslookup to see if you can resolve the host name. If
this approach fails, it might be that your system is not setup to use
DNS. The nslookup command depends on the network configuration, and,
in some cases, it is not used. Inspect the results returned by
nslookup z196p7de
When there is an error or the name is not found check the
settings in the DNS configuration file, 'resolv.conf'.
cat resolv.conf
The nslookup command might use the entries in the
resolv.conf file successfully. However, the system might use a
different method as defined by the entries in the resolv.conf file.
* Check the host entry in hosts and the nsswitch.conf file.
grep `hostname` hosts
A typical entry when local host file is used with a DNS server
to resolve host names.
grep hosts: nsswitch.conf
hosts: files dns
These entries, "files dns" shows that the system name resolution
looks to the /etc/hosts file first and if it is not found, it looks to
DNS.
*
* If you are starting the server as a non-root user, check the
file permission for the hosts file.
ls -l hosts
A file that is readable by the non-root user is similar to this entry:
rw-rw- r -- 1 root system 2590 Feb 14 12:33 hosts
If the non-root user does not have read access, ask your system
administrator to add the user to the group. Alternatively, run the
following command on UNIX systems to add read access:
chmod o+r /etc/hosts
* When the problem persists, use the Service Request (SR) tool to
open and send the previous information along with the details that are
requested in the following document:, MustGather: Read first for
WebSphere Process Server
You cannot start the server due to problems resolving the host name.
Symptom
When this problem occurs, the following information is written to the
SystemOut.log file after you try to start the server:
0000000a WsServerImpl E WSVR0009E: Error occurred during startup
META-INF/ws-server-components.xml
[3/15/11 9:16:28:750 CST] 0000000a WsServerImpl E WSVR0009E: Error
occurred during startup
com.ibm.ws.exception.ConfigurationError:
com.ibm.ws.exception.ConfigurationError:
javax.naming.ConfigurationException: Cannot get canonical host name
for server.
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:185)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:140)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:461)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:183)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:90)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:72)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:329)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:92)
Caused by: com.ibm.ws.exception.ConfigurationError:
javax.naming.ConfigurationException: Cannot get canonical host name
for server.
at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:269)
at com.ibm.ws.security.core.SecurityComponentImpl.initialize(SecurityComponentImpl.java:90)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:1338)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:1136)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:356)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:178)
... 24 more
Caused by: javax.naming.ConfigurationException: Cannot get canonical
host name for server.
at com.ibm.ws.security.core.SecurityConfig.getHostName(SecurityConfig.java:2875)
at com.ibm.ws.security.core.SecurityConfig.setValues(SecurityConfig.java:1247)
at com.ibm.ws.security.core.distSecurityComponentImpl.initializeSecurityConfig(distSecurityComponentImpl.java:816)
at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:247)
... 29 more
Cause
This problem occurs when the server is unable to look up the host name
that was used to create the profile.
Resolving the problem
To resolve this issue, complete the following actions:
* Determine the host name used for the server by looking in the
profile_root/config/cells/cell_name/nodes/node_name/serverindex.xml
file and then work with your network or operating system administrator
to correct the problem. Check the following network settings and
report the results to your system administrator.
* Check your system manuals or man page for the availability or
equivalent commands if you find any errors in execution or the
commands in the examples below. One example, you might find the ping
command with the "command not found" error and can correct by
proceeding the command with the fully qualified path,
"/usr/sbin/ping".
*
o Start a UNIX shell and change your working directory to
/etc to execute the commands in the following example. Your system
might also place the network configuration files with other names in
different locations. The example given is from AIX 6.1
cd /etc
o Use the hostname command to report the host name for the
system. In the following example, the host name is returned as
z196p7de.
hostname
z196p7de
o Use nslookup to see if you can resolve the host name. If
this approach fails, it might be that your system is not setup to use
DNS. The nslookup command depends on the network configuration, and,
in some cases, it is not used. Inspect the results returned by
nslookup z196p7de
When there is an error or the name is not found check the
settings in the DNS configuration file, 'resolv.conf'.
cat resolv.conf
The nslookup command might use the entries in the
resolv.conf file successfully. However, the system might use a
different method as defined by the entries in the resolv.conf file.
* Check the host entry in hosts and the nsswitch.conf file.
grep `hostname` hosts
A typical entry when local host file is used with a DNS server
to resolve host names.
grep hosts: nsswitch.conf
hosts: files dns
These entries, "files dns" shows that the system name resolution
looks to the /etc/hosts file first and if it is not found, it looks to
DNS.
*
* If you are starting the server as a non-root user, check the
file permission for the hosts file.
ls -l hosts
A file that is readable by the non-root user is similar to this entry:
rw-rw- r -- 1 root system 2590 Feb 14 12:33 hosts
If the non-root user does not have read access, ask your system
administrator to add the user to the group. Alternatively, run the
following command on UNIX systems to add read access:
chmod o+r /etc/hosts
* When the problem persists, use the Service Request (SR) tool to
open and send the previous information along with the details that are
requested in the following document:, MustGather: Read first for
WebSphere Process Server