vSAN Disk Management intermittently showing error "Unable to extract requested data. Check vSphere Client logs for details."
search cancel

vSAN Disk Management intermittently showing error "Unable to extract requested data. Check vSphere Client logs for details."

book

Article ID: 412890

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSAN 8.x

Issue/Introduction

  • When viewing Disk Management  under vsan cluster > Configure > vSan > Disk Management, the disks appear for a while but errors out afterwards with error :  

    Unable to extract requested data. Check vSphere Client logs for details.

 

  • vsphere_client_virgo.log under vCenter /var/log/vmware/vsphere-ui/logs reports some slowness :

[ERROR] p-nio-127.0.0.1-5090-exec-98 70008074 100482 200024 com.vmware.vise.actionsfw.impl.ActionsEvaluator                   An error occurred while retrieving data for actions evaluation. com.vmware.vise.data.query.internal.DataServiceException: The query execution timed out because of a back-end property provider 'Property provider com.vmware.vise.data.adapters.risetovise.RiseToVisePropertyProviderAdapter' which took more than 300 seconds.
        at com.vmware.vise.data.query.impl.DataManager.processPropertyProviderTaskException(DataManager.java:858)
        at com.vmware.vise.data.query.impl.DataManager.executeProperyProviderTasks(DataManager.java:827)
        at com.vmware.vise.data.query.impl.DataManager.invokePropertyProviders(DataManager.java:788)
        at com.vmware.vise.data.query.impl.DataManager.processPropertyProviderQueryResult(DataManager.java:646)
        at com.vmware.vise.data.query.impl.DataManager.getResultsFromPropertyProviders(DataManager.java:575)
        at com.vmware.vise.data.query.impl.DataManager.getResultsFromPropertyProviders(DataManager.java:528)
        at com.vmware.vise.data.query.impl.DataManager.getResultsFromPropertyProviders(DataManager.java:443)
        at com.vmware.vise.data.query.impl.DataServiceImpl.getResults(DataServiceImpl.java:336)
        at com.vmware.vise.data.query.impl.DataServiceImpl.getResponse(DataServiceImpl.java:203)
        at com.vmware.vise.data.query.impl.DataServiceImpl.getData(DataServiceImpl.java:177)
        at sun.reflect.GeneratedMethodAccessor516.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
        at com.sun.proxy.$Proxy249.getData(Unknown Source)
        at com.vmware.vise.data.adapters.risetovise.RiseToViseQueryExecutor.getData(RiseToViseQueryExecutor.java:478)
        at com.vmware.vise.data.adapters.risetovise.RiseToViseQueryExecutor.executeComplexQueriesInVise(RiseToViseQueryExecutor.java:279)
        at com.vmware.vise.data.adapters.risetovise.RiseToViseQueryExecutor.executeComplexQueries(RiseToViseQueryExecutor.java:207)
        at com.vmware.vise.data.adapters.risetovise.RiseToViseQueryExecutor.executeQueryBatch(RiseToViseQueryExecutor.java:152)
        at com.vmware.vise.data.adapters.risetovise.RiseToViseQueryServiceFactory$RiseToViseQueryBatchService.executeQueryBatch(RiseToViseQueryServiceFactory.java:142)
        at sun.reflect.GeneratedMethodAccessor1305.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)

 

  • vpxd.log under vCenter /var/log/vmware/vpxd path indicates some timeouts related to vsanhealth

2025-09-29T18:23:09.906Z info vpxd[06718] [Originator@6876 sub=vmomi.soapStub[1341] opID=WorkQueue-28ae8578] SOAP request returned HTTP failure; <<cs p:00007fbe1458e1b0, TCP:localhost:1080>, /vsanHealth>, method: querySpaceUsage; code: 500(Internal Server Error); fault: (vmodl.fault.SystemError) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    reason = "Exception('Waiting process is timeout.')"
-->    msg = "Received SOAP response fault from [<<cs p:00007fbe1458e1b0, TCP:localhost:1080>, /vsanHealth>]: querySpaceUsage
--> A general system error occurred: Exception('Waiting process is timeout.')"
--> }
2025-09-29T18:23:09.906Z warning vpxd[06718] [Originator@6876 sub=drmLogger opID=WorkQueue-28ae8578] Exception was thrown when call vsan-cluster-space-report-system for cluster [vim.ClusterComputeResource:domain-c4xxxx,ClusterName] vSAN dedup and compression savings data: N5Vmomi5Fault11SystemError9ExceptionE(Fault cause: vmodl.fault.SystemError
--> )
2025-09-29T18:23:09.911Z info vpxd[05830] [Originator@6876 sub=cdrsPlmt opID=WorkQueue-2d4c91d2] UpdateVsanStats worker is active, skip.
2025-09-29T18:23:09.912Z info vpxd[07669] [Originator@6876 sub=cdrsPlmt opID=WorkQueue-baa7a1e] UpdateVsanStats worker is active, skip.
2025-09-29T18:23:09.918Z info vpxd[05873] [Originator@6876 sub=vmomi.soapStub[1341] opID=WorkQueue-4c743e5] SOAP request returned HTTP failure; <<cs p:00007fbe1458e1b0, TCP:localhost:1080>, /vsanHealth>, method: querySpaceUsage; code: 500(Internal Server Error); fault: (vmodl.fault.SystemError) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    reason = "Exception('Waiting process is timeout.')"
-->    msg = "Received SOAP response fault from [<<cs p:00007fbe1458e1b0, TCP:localhost:1080>, /vsanHealth>]: querySpaceUsage
--> A general system error occurred: Exception('Waiting process is timeout.')"
--> }

 

  • vsanvcmgmtd.log under vCenter /var/log/vmware/vsan-health/ path also reports timeouts :


2025-09-29T19:53:59.470Z error vsanvcmgmtd[749288] [vSAN@6876 sub=Py2CppStub opID=WorkQueue-4bb0d92f-fd52] |-- EExit VSLM::vslm.vso.VStorageObjectManager.listVStorageObjectsForSpec (1800003 ms)
2025-09-29T19:53:59.470Z error vsanvcmgmtd[722376] [vSAN@6876 sub=IO.Http opID=WorkQueue-4bb0d92f-fd52] User agent failed to send request; (null), N7Vmacore16TimeoutExceptionE(Operation timed out)
2025-09-29T19:53:59.472Z info vsanvcmgmtd[749360] [vSAN@6876 sub=IO.Http opID=WorkQueue-55af0e9a-fd30] Terminating user agent request; (null), N7Vmacore16TimeoutExceptionE(Operation timed out)

 

Environment

vSphere 8.x , VMware vSAN 8.x

Cause

This occurs when ESXi hosts are updated or new ESXi hosts are added to vSAN cluster where ESXi hosts are in a later version than what vCenter Server version is currently running. This is currently not supported. Note that, this can affect all vSAN clusters within one particular vCenter even one or more ESXi hosts are in higher version only within one of the vSAN clusters. 

Resolution

To identify such hosts and rectify, follow resolution steps found in article : vCenter Server vpxd Service Repeatedly Stops After Reverting from 8.0 U3 to 8.0 U2.

Powered by Wolken Software