File service Node alert: Infrastructure Health - File service VM not found on this host.
search cancel

File service Node alert: Infrastructure Health - File service VM not found on this host.

book

Article ID: 393871

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

Symptoms:

  • Noticed alert "File service VM not found on this host" on vsan skyline summary.

 

Verification :

  • Verified that both the VDFS daemon and Sockrelay services were actively running on the affected ESXi host.

  • Confirmed that a valid certificate was present for vSAN File Services.

  • Verified that the overall vSAN cluster health status was reported as green.

  • Rebooted the vSAN File Services VM (FSVM); however, the issue persisted after the reboot.

Environment

VMware vSAN 7.x

VMware vSAN 8.x

Cause

  • The ESXi host was unable to communicate with the vSAN File Service VM.
  • A review of the /var/run/log/vsanmgmt.log revealed that the host was unable to locate the File Service VM. The relevant log entries are as follows:

2025-03-20T09:45:20.743Z Er(11) vsand[2101436]: [opID=50b84a2d-7e18 VsanFileServiceSystemImpl::validateFsvm] Failed to access power state of fsvm
2025-03-20T09:45:20.743Z Er(11)[+] vsand[2101436]: Traceback (most recent call last):

2025-03-20T07:10:19.700Z Er(11)[+] vsand[2101436]: AttributeError: 'NoneType' object has no attribute 'runtime'
2025-03-20T07:10:19.700Z Wa(12) vsand[2101436]: [opID=50b78aeb-62b0 VsanFileServiceSystemImpl::_CheckFsvmHealth] Health check: FSVM not found
2025-03-20T07:10:19.700Z In(14) vsand[2101436]: [opID=50b78aeb-62b0 VsanFileServiceSystemImpl::_CheckFsvmHealth] Finish checking fsvm health: (vim.host.VsanResourceHealth) {
2025-03-20T07:10:19.700Z In(14)[+] vsand[2101436]:resource = 'esxi-host',
2025-03-20T07:10:19.700Z In(14)[+] vsand[2101436]:health = 'red',
2025-03-20T07:10:19.700Z In(14)[+] vsand[2101436]:description = 'File service VM not found on this host.'

  • Upon further review of the /var/run/log/vsanmgmt.log, it was revealed that the host was unable to locate the File Service VM. The relevant log entries are as follows:

2025-03-20T07:10:19.718Z Er(11) vsand[2101436]: [opID=50b78aeb-62b0 VsanFileServiceLibrary::GetFsvmMemSizeInMB] Failed to query FSVM memory size
2025-03-20T07:10:19.718Z Er(11)[+] vsand[2101436]: Traceback (most recent call last):
2025-03-20T07:10:19.718Z Er(11)[+] vsand[2101436]:File "/usr/lib/vmware/vsan/perfsvc/VsanFileServiceLibrary.py", line 986, in GetFsvmMemSizeInMB
2025-03-20T07:10:19.718Z Er(11)[+] vsand[2101436]: KeyError: None

Resolution

To resolve the issue, the following steps are recommended:

  1. Place the affected ESXi host into maintenance mode using the Ensure Accessibility option. This ensures that no virtual machines are impacted during the troubleshooting process.

  2. Verify network connectivity between the ESXi host and the vSAN File Service VM (FSVM). This includes checking physical network links, validating IP configuration, and ensuring proper DNS resolution.

  3. Once the host is confirmed to be in maintenance mode and network connectivity is verified, reboot the affected ESXi host. Rebooting can help resolve transient issues, including communication failures with the FSVM.

  4. If the issue persists after the reboot, delete the vSAN File Service VM (FSVM) from the environment, and then exit the ESXi host from maintenance mode.

Alternatively:

  1. Once the host is in maintenance mode, within vCenter, move the host out of the cluster to the data center level in inventory, then move it back in. 

 

Powered by Wolken Software