If so, might be caused by the following:
VCP, CCE-V, MCSE Private Cloud certified virtualization specialist. Being doing the IT malarky over 20 years. Also sports nut for my troubles :)
Month: April 2016
If so, might be caused by the following:
Recently came across an issue on the VMware forums were user encountered numerous issues going to latest update on vSphere 6, reversion to the previous update resolved issue(corrupt driver).
Was interested to see VMware’s approach to a reversion and found this KB:
Oftentimes will see the above message when working within the VCSA appliance and needing to carry out admin functions.
To resolve:
i) Logon to the console eg https:<appliancename:5480 and enter your administrator id and password
ii) Click vCenter Server after logon
iii) Click the Summary tab
iv) Click on the Stop button to stop the server component
If the above doesn’t work (in most instances it should) then do the following:
i) Connect to the appliance’s console using putty or your SSH client of choice
ii) After logon type # chkconfig and check if vmware-vpxd is on or off
iii) if showing on you can stop it by entering # service vmware-vpxd stop
iv) When you need to start the server again simply enter # service vmware-vpxd start
If so advised to exclude the following file from synchronizing:
HKLM\Cluster\
.ShutdownTimeoutInMinutes
value according to your needs.