"Unable to query vSAN health information. Check vSphere Client logs for details" error in vSphere Client due to unresponsive host
search cancel

"Unable to query vSAN health information. Check vSphere Client logs for details" error in vSphere Client due to unresponsive host

book

Article ID: 427685

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSAN

Issue/Introduction

  • When navigating to the vSAN services tab in the vSphere Client, the following error message is displayed:

"Unable to query vSAN health information. Check vSphere Client logs for details"

  • The vsan-mgmt logs indicate a timeout while querying a specific host, with errors similar to:
    [ERROR] pool-5-thread-82 QueryExecutor [queryId: q-2590...] Data Provider 'VapiConnection(url=http://localhost:80/vsan/api)' threw error while executing query:
    ERROR vsan-mgmt[10906] [VsanVcObjectHelper::GetCallResultAndWait] Got exception in getting result : Waiting process is timeout.
    ERROR vsan-mgmt[10906] [VsanVcCapabilitySystemImpl::RetrieveHostCapabilities] Fail to get host capability for 'vim.HostSystem:host-##'
  • Additionally, the vsan-health summary logs (/var/log/vmware/vsan-health/vmware-vsan-health-summary-result.log) may show the cluster health degrading from green to yellow or red, with specific tests like hostconnectivity failing for a specific host.
    YYYY-MM-DDTHH:MM:SSZ INFO vsan-mgmt[1769627] [VsanHealthSummaryLogUtil::PrintHealthResult opID=22####66] Cluster ########  Overall Health : yellow
    YYYY-MM-DDTHH:MM:SSZ  INFO vsan-mgmt[27711] [VsanHealthSummaryLogUtil::PrintHealthResult opID=22####66] Cluster ########5  Overall Health :
    YYYY-MM-DDTHH:MM:SSZ  INFO vsan-mgmt[27505] [VsanHealthSummaryLogUtil::PrintHealthResult opID=22713b0a] Cluster ########  Overall Health : red
    YYYY-MM-DDTHH:MM:SSZ  INFO vsan-mgmt[67930] [VsanHealthSummaryLogUtil::PrintHealthResult opID=22####66] Cluster ######## Overall Health : red
  • In the vSphere Client inventory, the affected ESXi host may show "0" or blank values for CPU and Memory usage, indicating it is not sending statistics to vCenter.
  • Attempts to restart the vpxa service on the host may result in the host going into a "Not Responding" state.

Environment

 

  • VMware vSphere

  • VMware vSAN

 

Cause

The vSAN Health Service query times out because one or more ESXi hosts in the cluster are unresponsive. For example the unresponsiveness caused by underlying storage-related issues on the ESXi host, prevents the management agents (such as vpxa and vsan-mgmt) from responding to vCenter queries in a timely manner.

Resolution

To resolve the vSAN health query timeout and restore visibility to the rest of the cluster, you must isolate the problematic host.

  1. Identify the unresponsive host by checking the vsan-mgmt logs or observing which host in the vSphere Inventory is failing to report CPU/Memory statistics.

  2. Isolate the host from the cluster using one of the following methods:

    • Disconnect the Host: Right-click the unresponsive ESXi host in the vSphere Client and select Connection > Disconnect.

    • Maintenance Mode: If possible, place the host into Maintenance Mode.

  3. Investigate and resolve the underlying storage issues on the affected ESXi host (e.g., hardware health, storage controller status).

  4. Once the storage issues are resolved and the host is healthy:

    • Exit Maintenance Mode or Reconnect the host to vCenter.

    • Verify that vSAN health queries are functioning correctly.