vCSA Console Problems

vCSAI have been having problems trying to connect to the console of VM’s from the vCSA for what seems like forever. After numerous conversations with peers there just always seemed to be this issue or that issue. What worked for one did not work for another, and none of the solutions seemed to work for me.

Well all that changed last week. I finally was able to resolve my issues and without a doubt can say I can now connect to the console across most of my platforms, ok Windows and Mac (Linux seems to be an after thought since the console relies on flash and that has been discontinued for Linux).

What was the solution you may ask. Well if you can believe it VMware ships the vCSA broken. I hear your skepticism, but no it is true. The root cause is a missing environment variable.

VMWARE_JAVA_HOME

The solution is toe SSH into the vCSA, and edit the wrapper.conf file. This file is located in /usr/lib/vmware-vsphere-client/wrapper/conf.

You basically need to append the # Environment Variables section and add the following line:

set.default.VMWARE_JAVA_HOME=/usr/java/jre-vmware
  • For example, modify the default configuration file to:
  • Save and close the wrapper.conf file.
  • Restart the vSphere Web Client using this command:
/etc/init.d/vsphere-client restart

This fixed it for me, yay! The thing that irritates me is that this is a VMware designed, built and delivered as a virtual appliance. They should simply fix this and make it part of the next version.

Note: this issue has now been documented in VMware KB (2060604)
HTML5 virtual machine console fails to open after restarting VMware vCenter Server Appliance 5.5

Leave a Reply

Your email address will not be published. Required fields are marked *

*