Error "com.vmware.vsan.perfsvc.fault.queryperf.timeout" is observed when vSAN performance data gathering fails.
search cancel

Error "com.vmware.vsan.perfsvc.fault.queryperf.timeout" is observed when vSAN performance data gathering fails.

book

Article ID: 438919

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

  • Performance data for a vSAN Cluster is not available in the vCenter Server.
  • Aria Operations may report the error "Statistics collection of vSAN Performance Service is not working correctly."
  • vpxd logs in the vCenter Server has the below errors

    info vpxd[33575] [Originator@6876 sub=vmomi.soapStub[159] opID=SWI-30b36fd5] SOAP request returned HTTP failure; <<io_obj p:0x00007ff6e42b7d38, h:57, <TCP '127.0.0.1 : 51256'>, <TCP '127.0.0.1 : 80'>>, /vsanHealth>, method: queryVsanPerf; code: 500(Internal Server Error); fault: (vim.fault.Timedout) {
    -->    faultCause = (vmodl.MethodFault) null,
    -->    faultMessage = (vmodl.LocalizableMessage) [
    -->       (vmodl.LocalizableMessage) {
    -->          key = "com.vmware.vsan.perfsvc.fault.queryperf.timeout",
    -->          arg = <unset>,
    -->          message = "Operation timeout. No performance data responded from vSAN datastore in expected time period (40 seconds)."
    -->       }
    -->    ]
    -->    msg = "Received SOAP response fault from [<<io_obj p:0x00007ff6e42b7d38, h:57, <TCP '127.0.0.1 : 51256'>, <TCP '127.0.0.1 : 80'>>, /vsanHealth>]: queryVsanPerf
    --> Received SOAP response fault from [<SSL(<io_obj p:0x00007f468810fea8, h:146, <TCP '<vCenter IP address> : 59542'>, <TCP '<vSAN Master Node IP> : 443'>>), /vsan>]: queryVsanPerf
    --> Operation timeout. No performance data responded from vSAN datastore in expected time period (40 seconds)."
    --> }

Environment

vSAN 7.x
vCenter 7.x
ESXi 7.x

Cause

  • The error "com.vmware.vsan.perfsvc.fault.queryperf.timeout" indicates that the vCenter Server did not receive the requested performance data from the vSAN Master host within the hardcoded 40-second timeout period.

Resolution

  • Investigate if the vSAN master host is healthy and responsive.
  • Reboot the ESXi host to change the vSAN master node if it is not responding.