"Unable to extract requested data. Check vSphere Client logs for details."
This may not be a vSAN FS specific issue - a lot of the vSAN-related vSphere UI tabs rely on the vmware-vsan-health service running on vCenter - can you check whether it shows the same error banner at: Cluster > Monitor > vSAN > Skyline Health > Retest ?
If yes (and/or anyway I guess as it shouldn't be disruptive), you can start with restarting the vmware-vsan-health service using:
# service-control --stop vmware-vsan-health
# service-control --start vmware-vsan-health
The vmware-vsan-health service logs are located on vCenter at /var/log/vmware/vmware-vsan-health/ .
Original Message:
Sent: May 16, 2025 03:15 AM
From: RaoulSchaffner
Subject: vSAN OSA File Service: How to deconfigure without GUI?
Dear all,
one remark at the beginning: this is all happening in a test setup, no prod involved.
I've successfully setup a vSAN OSA configuration in a 4-node cluster with the latest ESXi.
I've even made this vSAN storage available to a secondary 2-node compute-only cluster.
All good.
Then I wanted to experiment with "vSAN Data Protection" but learned that it only works with ESA.
Then I wanted to experiment with "File Service" and got it somewhat running, the Fileservice ESX Agents were deployed on every node of the vSAN cluster. However, the configuration regarding the domain never got deployed correctly. Now it's in limbo.
In the cluster configuration view, the File Service section shows:
- File Service: Disabled
- Red Banner "Unable to extract requested data. Check vSphere Client logs for details."
- the "Edit" link that would normally show in the lower left corner is replaced by a spinning circle
Questions:
- where can I find the vSphere Client logs?
- How can I deconfigure this setup without GUI (the Edit link is not available) if I don't find any hints in the logs?
Thank you very much,
Raoul.