MKS Error on two hosts in a four host cluster - vSphere 5.5
Could not create console connection to certain VMs either through vSphere client or web client with Error message: Unable to connect to MKS: A general system error occurred: Internal error
After investigating some more it was only VMs on two of the hosts in a four host cluster. Enabled SSH on one of the affected hosts to restart mgmt services but got error message "Network error: Connection refused". Same on the other affected host but could connect with SSH to the other hosts with no issue.
Tried from vCenter server but same result. Rebooted vCenter server but same result.
Logged on to console session on both dodgy hosts and did management services restart - still cannot ssh to them and still cannot do a console session to VMs, however error message changed to Error Message: Unable to connect to server IPAddress:902
Logged on to shell and did a vdf -h but no issues with full root ramdisk or anything obvious.
Also cannot vmotion anything off the affected hosts and would prefer not to have to shut doen the VMs (which appear to be working fine) so any ideas or pointers please? Will log with VMWare support in the morning but like to fix myself if possible.
After investigating some more it was only VMs on two of the hosts in a four host cluster. Enabled SSH on one of the affected hosts to restart mgmt services but got error message "Network error: Connection refused". Same on the other affected host but could connect with SSH to the other hosts with no issue.
Tried from vCenter server but same result. Rebooted vCenter server but same result.
Logged on to console session on both dodgy hosts and did management services restart - still cannot ssh to them and still cannot do a console session to VMs, however error message changed to Error Message: Unable to connect to server IPAddress:902
Logged on to shell and did a vdf -h but no issues with full root ramdisk or anything obvious.
Also cannot vmotion anything off the affected hosts and would prefer not to have to shut doen the VMs (which appear to be working fine) so any ideas or pointers please? Will log with VMWare support in the morning but like to fix myself if possible.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Paul Solovyovsky
also try logging directly to the hosts, vs vcenter via vi client.
ASKER
Some of the VMs hosts part of a large SharePoint farm so do not really want to shut down VMs if possible. Also connects Ok to host direct with client but still same issues on VMs.
If you have a fault, you will need to schedule emergency downtime, is your Sharepoint Farm not designed with failure in the design ?
ASKER
Andrew. Thanks for taking the time to reply. SharePoint has failover but was just trying to avoid but looking like we will have to go down that route anyway. Had a similar issue a few months back and reboot did clear it but never found out what caused it so this time wanted to try and see what it was.
I would encourage you to, make sure hosts and vCenter Server are on the latest releases.
you can always open a ticket with vmware and send them over the logs, seems like this happens from time to time.
Have you checked the Security Profile / Firewall settings to make sure it is not blocking connections... probably not but always worth a check
ASKER
Apologies for not getting back. Ended up rebooting hosts to fix and awaiting VMWare response to logs.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for ncht's comment #a40934630
for the following reason:
VMWare support fixed the issue.
Accepted answer: 0 points for ncht's comment #a40934630
for the following reason:
VMWare support fixed the issue.
My first post http:#a40844803 states Shutdown VMs and Restart Hosts!
ASKER
Andrew,
Apologies, had a quick scan and did not pick up on your post. Had done previously to fix as I said in a later post but wanted to try and isolate what was causing it. Happy to give you the points.
Apologies, had a quick scan and did not pick up on your post. Had done previously to fix as I said in a later post but wanted to try and isolate what was causing it. Happy to give you the points.