Skip to main content

"vSAN Health service installation" failed on a host

 

Symptoms
" vSAN Health Service - Cluster Health - vSAN Health service installation" failed on a host in cluster.
 
and may see the following error at the same time:
a. The disk group on the failed host reports "0 of 0" under "Configure-Disk Management-Disk Groups" in “Disks in Use" column.
b. vCenter webclient may reports "The query exection timed out because of a back-end property provider 'com.vmware.vsphere.client.vsan.health.VsanHealthPropertyProvider' which took more than 120 seconds.
 
Purpose
Help troubling "vSAN Health Service - Cluster Health - vSAN Health service installation" failure.
Cause
vsanmgmtd service is not running on the host.
Impact / Risks
The vSAN Health Service does not work.
Resolution
Verify the vsanmgmtd service on all hosts in the vSAN cluster with
/etc/init.d/vsanmgmtd status
 
If it is not running, start it with
/etc/init.d/vsanmgmtd restart
 
Verify if this issue is resolved.

Comments

Post a Comment

Popular posts from this blog

Cloning and converting virtual machine disks with vmkfstools

 Purpose This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another. Resolution The vmkfstools command offers the ability to clone virtual machine content and also convert from one virtual machine disk ( .vmdk ) format into another. Note : The host operating system chosen to perform the conversion may not necessarily support running of virtual machines via the output format defined. vmkfstools maintains the possibility of exporting virtual disks for use in other VMware products which support alternative disk formats. To convert a virtual machine disk from one type to another: Shut down the virtual machine. Virtual machine disk files are locked while in-use by a running virtual machine. Log in to the VMware vSphere Management Assistant (v...
Post a Comment
Read more

Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.5, 6.7 and 7.0

  Purpose This article provides steps to increase the disk space of a specific VMDK for the vCenter Server Appliance 6.5, 6.7 and 7.0. With the introduction of Logical Volume Management (LVM) in vSphere 6.0 and continued support with vSphere 6.5, 6.7 and 7.0, the vCenter Server disks can be dynamically increased. List of VMDKs for a vCenter Server Appliance 6.5 - Size Mount point and Purpose Note : Resizing the root partition (VMDK1 listed in the KB above) is not supported on 6.5. Please see the vSphere 6.5 Release Notes for more information. Resizing root partition has been added to 6.7 and 7.0. List of VMDKs/Partitions for a vCenter Server Appliance 6.7 - Size Mount point and Purpose   List of VMDKs/Partitions for a vCenter Server 7.0 - Size Mount point and Purpose Note : This KB can be used for the situation like SEAT partition full or any other vCenter appliance partition full. ...
Post a Comment
Read more

Troubleshooting vpxd service on Windows vCenter Server

  Symptoms You cannot connect to VMware vCenter Server with the vSphere Client. You cannot see the VMware vCenter Server in the inventory in the vSphere Web Client. You see a Microsoft Windows Event error associated with IIS similar to: Event properties - Event 7024, Service Control Manager The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified.. Log Name: System Source: Service Control Event ID: 7024 Level: Error Note : A windows Event ID 1000 may also be reported in relation to this issue.   Connecting to vCenter Server fails with the error: Cannot connect to host server_name : No connection could be made because the target machine actively refused it.   Attempting to start the VMware VirtualCenter Server service fails. You see this error: Windows could not start the VMware VirtualCenter Server service on...
Post a Comment
Read more