Symptoms
- The HTML5 virtual machine console fails to open after restarting the vCenter Server Appliance (VCSA).
- Opening the HTML5 console of a virtual machine fails.
- You see an error similar to:
Could not connect to VCSA_Address:7331 - The vsphere_client_virgo.log file (located at: /var/log/vmware/vsphere-client/logs/)contains entries similar to:
[YYYY-MM-DD 15:12:37.938] [WARN ] Thread-39 com.vmware.mks.LifeCycleManager Process has unexpetedly ended with exception: org.apache.commons.exec.ExecuteException: Execution failed (Exit value: -559038737. Caused by java.io.IOException: Cannot run program "java" (in directory "/usr/lib/vmware-vsphere-client/server/work/tmp/console-distro"): error=2, No such file or directory)
Cause
Resolution
This is a known issue affecting vSphere Web Client 5.5 running in VCSA 5.5.
To work around this issue, set the VMWARE_JAVA_HOME environmental variable to /usr/java/jre-vmware.
To set the VMWARE_JAVA_HOME environmental variable:
- Connect to the vCenter Server Appliance via SSH as the root user.
Note: To enable SSH on the vCenter Server Appliance 5.5, see Enable or Disable SSH Administrator Login on the VMware vCenter Server Appliance in the vCenter Server and Host Management Guide. - Open the wrapper.conf file (located at: /usr/lib/vmware-vsphere-client/server/wrapper/conf/) using a text editor. For more information, see Editing files on an ESX host using vi or nano (1020302).
- Add this line under the Environmental Variables section:
set.default.VMWARE_JAVA_HOME=/usr/java/jre-vmware
For example, modify the default configuration file to:
# Environment Variables
##################
# Location of virgo server directory
set.VIRGO_KERNEL_HOME=/usr/lib/vmware-vsphere-client/server
# Location of NGC instance directory
set.default.INSTANCE_DIR=/user/lib/vmware-vsphere-client/server
set.default.CONFIG_DIR=%INSTANCE_DIR%/configuration
set.default.JMX_PORT=9875
set.default.LOG_DIR=/var/log/vmware-vsphere-client/server
set.default.VMWARE_JAVA_HOME=/usr/java/jre-vmware - Save and close the wrapper.conf file.
- Restart the vSphere Web Client using this command:
/etc/init.d/vsphere-client restart
Note: If the issue persists, you may need to reboot the vCenter Server Appliance and restart the vSphere Web Client again.
Source:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2060604
No comments:
Post a Comment