Recv Error 104 Connection Reset By Peer Vmware
Contents |
This article provides information on possible causes and how to troubleshoot when after reloading a virtual machine, console access fails with the error: "Unable to connect vmware unable to connect to the mks the operation is not allowed in the current state to the MKS: The operation is not allowed in the current state".
Vsphere 6 Unable To Connect To The Mks Could Not Connect To Pipe
Environment: VMware vSphere 5.5 Symptoms: After performing a virtual machine reload, you are unable to access the console. vmautomation connection error (1) on connection After reloading a virtual machine, the console is black and you are unable to use it. This issue occurs when your backup software reloads the virtual machine before or after https://kb.vmware.com/kb/2063262 a backup operation. After reloading a running virtual machine, the console displays the error:Unable to connect to the MKS: The operation is not allowed in the current state. This issue occurs when you reload the virtual machine via SSH using the command:vim-cmd vmsvc/reload The vmware.log file for the affected virtual machine (located at /vmfs/volumes/Datastore_of_affected_virtual_machine/Affected_virtual_machine_directory/) contains entries similar to:YYYY-MM-DDT00:00:22.467Z| vmx| I120: VmdbPipeStreamsOvlError http://www.dell.com/support/Article/SLN288157/EN Couldn't read: OVL_STATUS_EOF, (11) Resource temporarily unavailable.YYYY-MM-DDT00:05:59.773Z| mks| I120: SSL: syscall error 104: Connection reset by peerYYYY-MM-DDT00:05:59.773Z| mks| I120: SOCKET 2 (120) recv error 104: Connection reset by peerYYYY-MM-DDT00:06 :23.428Z| vmx| I120: Vix: [942082 mainDispatch.c:2886]: VMAutomation: Connection Error (4) on connection 2. Resolution: This is a known issue affecting ESXi 5.5. Currently, there is no resolution. To work around this issue, perform one of these options to restart the Virtual Network Computing (VNC) console service of the virtual machine: vMotion the affected virtual machine to another ESXi host. Restart the virtual machine from the vCenter Server or ESXi host. Reference: Unable to connect to the MKS: The operation is not allowed in the current state Quick Tips content is self-published by the Dell Support Professionals who resolve issues daily. In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolving an issue. As such Quick Tips have not been reviewed, validated or approved by Dell and should be used with appropriate c
Links Notable Members Current Visitors Recent Activity New Profile Posts Search Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only https://hardforum.com/threads/stuck-vms-looking-for-help-please.1826943/ Search this forum only Display results as threads More... Recent Posts Menu Log http://www.probableanswer.com/anwsers/485544/quot-stuck-quot-VMs-looking-for-help-please in or Sign up [H]ard|Forum Forums > Bits & Bytes > Virtualized Computing > "stuck" VMs - looking for help, please Discussion in 'Virtualized Computing' started by Eulogy, Jul 19, 2014. Jul 19, 2014 #1 Eulogy 2[H]4U Messages: 2,078 Joined: Nov 9, 2005 Have an odd dilemma, and I'm trying unable to to find the root cause of this instead of band-aid'ing it. Recently, my trusty C6100 died. After much troubleshooting, I decided to just buy a new, similar system off eBay. I found one, bought it, and received it yesterday. Of note, the C6005 I bought was damaged in transit. I notified the seller, and he's giving me the weekend to play/test it to try unable to connect to make sure it's OK. Old system was dual Intel L5560s, 48GB DDR3 ECCs / node. New system is dual AMD 2419 EEs, 48 GB DDR3 ECC. So definitely some architecture change. Regardless, I setup the system in a near identical way as my old one was. My evaluation licenses only had a couple of weeks left, so I just re-installed new everything. Each node has it's own 4GB USB drive, running 5.5 1331820. I spun up a vCetner VM and got it configured. Within vCenter, I created a new data center, and a cluster underneath that containing all three of the "new" nodes. Initially, I had HA and DRS enabled on the cluster. In troubleshooting, I disabled HA. Outside of the cluster, I have one standalone host that's running 5.1.0 1157734. Within the cluster I have 15 VMs, 12 of which run 24x7. The majority of these are Server 2012 R2, but there is also a CentOS machine, plus various VMWare appliances. Of the 12 that are running, it seems that any one of them will periodically (random interval from an hour to 3 hours it seem
off eBay. I found one, bought it, and received it yesterday. Of note, the C6005 I bought was damaged in transit. I notified the seller, and he's giving me the weekend to play/test it to try to make sure it's OK. Old system was dual Intel L5560s, 48GB DDR3 ECCs / node. New system is dual AMD 2419 EEs, 48 GB DDR3 ECC. So definitely some architecture change. Regardless, I setup the system in a near identical way as my old one was. My evaluation licenses only had a couple of weeks left, so I just re-installed new everything. Each node has it's own 4GB USB drive, running 5.5 1331820. I spun up a vCetner VM and got it configured. Within vCenter, I created a new data center, and a cluster underneath that containing all three of the "new" nodes. Initially, I had HA and DRS enabled on the cluster. In troubleshooting, I disabled HA. Outside of the cluster, I have one standalone host that's running 5.1.0 1157734. Within the cluster I have 15 vms, 12 of which run 24x7. The majority of these are Server 2012 R2, but there is also a CentOS machine, plus various VMWare appliances. Of the 12 that are running, it seems that any one of them will periodically (random interval from an hour to 3 hours it seems) get "stuck". Meaning, I cannot RDP to it, and when I try to connect to the console, sending Ctrl+Alt+Del has no effect (I do not get taken to the windows login prompt). On the login screen, the time is visibility "stuck" as well - no longer incrementing as it should (right now on the console of the ones that are "stuck" they show 1:20pm, it is 1:32pm). Interestingly enough, the machines still reply to PINGs. The vmware.log file doesn't show a thing out of the ordinary for these stuck vms. Here's the log entries around one of the vms that got "stuck" at 1:20: Code: 2014-07-19T18:59:20.399Z| vmx| I120: TOOLS received request in VMX to set option 'synctime' -> '0' 2014-07-19T18:59:20.465Z| vmx| I120: VMXVmdb_SetCfgState: cfgReqPath=/vm/#_VMX/vmx/cfgState/req/#4/, remDevPath=/vm/#_VMX/vmx/vigor/setCfgStateReq/#82/in/ 2014-07-19T20:16:25.450Z| mks| I120: SOCKET 3 (122) Creating VNC remote connection. 2014-07-19T20:27:19.348Z| mks| I120: SSL: syscall error 104: Connection reset by peer 2014-07-19T20:27:19.349Z| mks| I120: SOCKET 3 (122) recv error 104: Connection reset by peer 2014-07-19T20:27:19.349Z| mks| I120: SOCKET 3 (122) VNC Remote Disconnect. 2014-07-19T20:27:28.982Z| mks| I120: SOCKET 4 (122) Creating VNC remote connection. 2014-07-19T20:29:56.127Z| mks| I120: SSL: syscall error 104: Connection reset by peer 2014-0