Could not connect to https://vcenter_address:7331/ – Arun’s blog https://arunns.net Arun's blog Mon, 10 Feb 2014 10:40:17 +0000 en-US hourly 1 https://wordpress.org/?v=6.4.2 Could not connect to vmware console https://vcenter_address:7331/ https://arunns.net/could-not-connect-to-vmware-console-httpsvcenter_address7331/ https://arunns.net/could-not-connect-to-vmware-console-httpsvcenter_address7331/#respond Mon, 10 Feb 2014 10:40:17 +0000 http://arunnsblog.com/?p=781 This usually happens from the vSphere web client while opening a console session with virtual machine.

and the log (/var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log) shows something like:

[ERROR] Thread-42 System.err
INFO:oejsh.ContextHandler:started o.e.j.w.WebApp Context{/console,file:/tmp/jetty-0.0.0.0-7331-console.war-_console-any-/webapp/},/usr/lib/vmware-vsphere-client/server/work/tmp/console-distro/webapps/console.war

To fix this set the environment variable VMWARE_JAVA_HOME to proper path:

– SSH to vcenter
# vi /usr/lib/vmware-vsphere-client/server/wrapper/conf/wrapper.conf

– Under Environment variables add:
set.default.VMWARE_JAVA_HOME=/usr/java/jre-vmware

– Restart vsphere-client
# /etc/init.d/vsphere-client restart
Stopping VMware vSphere Web Client...
Stopped VMware vSphere Web Client.
Starting VMware vSphere Web Client...
Intializing registration provider...
Getting SSL certificates
Service with name was updated.
Return code is: Success
Waiting for VMware vSphere Web Client......
running: PID:

Reference: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2060604

]]> https://arunns.net/could-not-connect-to-vmware-console-httpsvcenter_address7331/feed/ 0