VMware Cloud Community
philippBr
Contributor
Contributor
Jump to solution

VMRC freezes after 30-60 seconds

Hey community,

i have the problem that Web Console is frozen after 30-60 seconds after connecting to a VM: No change of picture, No mouse/keyboard control.

Only thing i can do: Close and Re-Open the VMRC

VMWare ESXi: 6.7.0 Update 1 (Build 13004448)

vCenter Appliance: 6.7.0.21000

VMRC Version: 10.0.0.4

Tried two different Win10 Desktop-PC with Google Chrome, No AV Software installed

Here the logs from one connection which ended 2019-04-12T03:59:01

vmware-mks.log from the windows-pc which launches the VMRC

2019-04-12T03:58:15.304-07:00| mks| I125: GDI-Backend: successfully started by HWinMux to do window composition.

2019-04-12T03:58:15.304-07:00| mks| I125: Win32AllowDnDProxyMessages: Registered setProp: 0xC225

2019-04-12T03:58:15.304-07:00| mks| I125+                             Registered removeProp: 0xC21E

2019-04-12T03:58:15.304-07:00| mks| I125+                             Registered attachThreadProxy: 0xC223

2019-04-12T03:58:15.335-07:00| mks| I125: MKS-HWinMux: Started GDI presentation backend

2019-04-12T03:59:01.955-07:00| mks| W115: SOCKET 3 (-1) AsyncNamedPipeRecvCallback: failed to get overlapped result: 109.

2019-04-12T03:59:01.955-07:00| mks| I125: MKSControlSocket:  MKSControl Remote Disconnect: socket closed.

2019-04-12T03:59:01.955-07:00| mks| I125: MKSControlMgr: disconnected

2019-04-12T03:59:01.955-07:00| mks| I125: VmdbPipeStreamsOvlError: write failed, draining reads

2019-04-12T03:59:01.971-07:00| mks| I125: VmdbPipeStreamsOvlError Couldn't read: (109) The pipe has been ended.

2019-04-12T03:59:01.971-07:00| mks| I125: VmdbPipeStreamsOvlError Couldn't initiate write: (109) The pipe has been ended.

2019-04-12T03:59:01.971-07:00| mks| I125: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (-31)

2019-04-12T03:59:01.971-07:00| mks| I125: VmdbCnxRecvTuples failed: (-31) Pipe: Write failed

2019-04-12T03:59:01.971-07:00| mks| I125: VmdbCnxRecvSection failed: TUPLES (-31) Pipe: Write failed

2019-04-12T03:59:01.971-07:00| mks| I125: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'

2019-04-12T03:59:01.971-07:00| mks| I125: MKS: Requesting exit due to VMDB disconnect.

2019-04-12T03:59:01.971-07:00| mks| I125: GDI-Backend: stopped by HWinMux to do window composition.

2019-04-12T03:59:01.971-07:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 0.

2019-04-12T03:59:01.971-07:00| main| I125: MKS thread is stopped

2019-04-12T03:59:01.971-07:00| main| I125: REMOTEMKS: Powering off VNC Client

2019-04-12T03:59:01.971-07:00| main| I125: VNC CLIENT: Destroying VNC Client socket.

2019-04-12T03:59:01.971-07:00| main| I125: SOUNDLIB: Closing Wave sound backend.

2019-04-12T03:59:01.971-07:00| main| I125: MKSRoleMain: Powering off.

2019-04-12T03:59:01.971-07:00| main| I125: MKSRoleMain: Powering off MKS

2019-04-12T03:59:01.971-07:00| main| I125: MKS thread was already stopped

2019-04-12T03:59:01.971-07:00| mks| I125: MKS-RenderMain: Stopping MKSBasicOps

2019-04-12T03:59:01.971-07:00| mks| I125: MKS PowerOff

2019-04-12T03:59:01.971-07:00| mks| I125: MKS thread is exiting

2019-04-12T03:59:01.971-07:00| main| I125: MKSRoleMain: Exiting...

2019-04-12T03:59:01.971-07:00| main| I125: MKSRoleMain: Exiting MKS

2019-04-12T03:59:01.971-07:00| main| I125: WQPoolFreePoll : pollIx = 1, signalHandle = 800

2019-04-12T03:59:01.971-07:00| main| I125: MKSRoleMain: Exiting WorkerLib

2019-04-12T03:59:01.971-07:00| main| I125: WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

2019-04-12T03:59:01.971-07:00| main| I125: MKSRoleMain: Exiting Sig

2019-04-12T03:59:01.971-07:00| main| I125: MKSRoleMain: Exiting SSL

2019-04-12T03:59:01.971-07:00| main| I125: MKSRoleMain: Exiting Poll

2019-04-12T03:59:01.971-07:00| main| I125: MKSRoleMain: Exiting Log

vmrc-log from the windows pc which launches VMRC:

2019-04-12T03:58:14.460-07:00| vmrc| I125: VMClient_ConnectMksClientEx

2019-04-12T03:58:14.460-07:00| vmrc| I125: VMClient_ConnectMksClientEx - trying remote socket connection to esx1.merkca.com:902 /vmfs/volumes/5ca20f34-87240d36-a56f-0c9d92c4961f/VM-16 1/VM-16 1.vmx

2019-04-12T03:58:14.460-07:00| vmrc| I125: VMClientConnectSocketEx

2019-04-12T03:58:14.726-07:00| vmrc| I125: VMClient_ConnectMksClientEx - connecting the MKS client

2019-04-12T03:58:14.726-07:00| vmrc| I125: VMClientConnectMKSClientEx

2019-04-12T03:58:14.898-07:00| vmrc| I125: VmdbAddConnection: cnxPath=/db/connection/#3/, cnxIx=1

2019-04-12T03:58:15.179-07:00| vmrc| I125: VMMgr: Finished opening VM at /vm/#_3F357E0_vm-43/ from 172.16.16.2:vm-43

2019-04-12T03:58:15.179-07:00| vmrc| I125: VmdbCnxControlCb: registered SUBSCRIBE completion callback, cnx = /db/connection/#3/

2019-04-12T03:58:15.194-07:00| vmrc| I125: vmClientCore::VMWindow::SetVirtualScreenSize: Denied resize request because target size == current guest size

2019-04-12T03:58:15.194-07:00| vmrc| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: main UI rect: 1599x915 @ 208,208

2019-04-12T03:58:15.194-07:00| vmrc| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: Found 1 present screens

2019-04-12T03:58:15.194-07:00| vmrc| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: Windows for extra guest monitors will not be shown

2019-04-12T03:59:01.955-07:00| vmrc| I125: VMMgr::OnVMDestroyed: cleaning up after destroyed VM at /vm/#_3F357E0_vm-43/

2019-04-12T03:59:01.955-07:00| vmrc| I125: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#3/'

2019-04-12T03:59:01.955-07:00| vmrc| I125: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#3/' (0)

2019-04-12T03:59:01.955-07:00| vmrc| W115: Destroyed VmdbCnx object with 1 pending, async transactions.

2019-04-12T03:59:01.955-07:00| vmrc| I125: MKSWindowTrans: The current transaction 40476E8 has not been submitted.

Any idea how get this solved?

0 Kudos
1 Solution

Accepted Solutions
philippBr
Contributor
Contributor
Jump to solution

seems to be a heartbeat problem between esx host and vcenter....i removed NAT between those (which isnt supported anyway) and re-installed within same subnet as the host.

For now Remote console is stable

View solution in original post

0 Kudos
1 Reply
philippBr
Contributor
Contributor
Jump to solution

seems to be a heartbeat problem between esx host and vcenter....i removed NAT between those (which isnt supported anyway) and re-installed within same subnet as the host.

For now Remote console is stable

0 Kudos