Hello
We are having the typical Disconnected Console when trying for a Console in vCloud Director 5.5.2 issue. However after going through a lot of the basics we can see whats going on but not sure of the why =)
Has anyone seen information that I’ve identified lower down in the logs?
We have 2 machines going to the same cell, one works one doesn’t. so we stood up a new machine with the plugin from the machine that work installed. Unfortunately that machine didn’t work from the get go.
VMware Client Intragration Plug-in 5.5.0
Version 5.5.0.1879803 – working on vCenter server. Not working on a new machine.
VMware Client Intragration Plug-in 5.5.0
Version 5.5.0.1896808 – not working on another vcenter. Noticed this plugin is the vSphere Web Client delivered one.
Have checked time sync between cells. Aok.
Dns resolution is fine. From everywhere to everywhere, also across the proxy nic. No firewalls involved.
Main and proxy IP are on same subnet. Aok.
Machine requesting console is on same subnet as vCloud. Aok.
Checked https://<Console Proxy Address>/sdk/vimServiceVersions.xml and see if it loads. Aok.
vCloud director debug log (vCloud-container-debug.log) contains of interest
2014-12-04 09:48:46,545 | DEBUG | VsmEventListener-10.11.0.64 | EventListener | Event -1 received with event code : 210,001 |
2014-12-04 09:48:46,545 | DEBUG | VsmEventListener-10.11.0.64 | EventListener | Event code 210,001 will be handled by class com.vmware.vcloud.fabric.nsm.event.handlers.KeepAliveEventHandler |
1879329/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:379]: VM control has not been created
2014-12-04 10:13:34.863 [d:/build/ob/bora-1879329/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: shutdown called
Client Plugin log entries of interest
%userprofile%\AppData\Local\Temp\2\vmrc-plugin
1879329/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:379]: VM control has not been created
2014-12-04 10:13:34.863 [d:/build/ob/bora-1879329/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: shutdown called
** Versus a successful plugin log entry
1896274/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: Binding to [VMRC_MONIKER_vmrc-np-t-{88C192D4-B380-473D-B7F7-FC0CD768C4A2}]
2014-12-04 10:22:45.570 [d:/build/ob/bora-1896274/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject succeeded
2014-12-04 10:22:45.580 [d:/build/ob/bora-1896274/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: startup succeeded
2014-12-04 10:22:46.849 [d:/build/ob/bora-1896274/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
2014-12-04 10:22:46.849 [d:\build\ob\bora-1896274\bora\apps\vmplayer\npplugin\win32\../../plugin-common/utils.h:145]: Advanced config parsed into the features: 3
2014-12-04 10:22:46.850 [d:/build/ob/bora-1896274/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: Startup: VMRC_MONIKER_vmrc-np-t-{8D8718E5-8B82-42CF-863D-0B726147D456}, VMRC_EVENT_vmrc-np-t-{8D8718E5-8B82-42CF-863D-0B726147D456}, C:\Program Files (x86)\Common Files\VMware\VMware Remote Console Plug-in 5.5\Firefox\vmware-vmrc.exe, "C:\Program Files (x86)\Common Files\VMware\VMware Remote Console Plug-in 5.5\Firefox\vmware-vmrc.exe" --parent-PID 8492 --instance-ID "vmrc-np-t-{8D8718E5-8B82-42CF-863D-0B726147D456}" --modes 4 --message-mode 2 --features 3