'File service VM not found on the host, Socketrelay is not running' alert seen on vSAN cluster skyline health.

Products

• VMware vSAN

Issue/Introduction

Skyline health reports vSAN file service node alert: File service VM not found on this host:

The host reporting the alert does not have any FS VMs running on it.

Environment

VMware vSAN 7.x

VMware vSAN 8.x

Cause

EAM service on the vCenter having issues can cause the FS VMs to not be re-deployed and can in turn lead to the error 'File service VM not found on this host'.

The EAM logs under /var/log/vmware/eam report the below error:

com.vmware.eam.security. NotAuthenticated: Failed to authenticate extension com.vmware.vim.eam to vCenter.
com.vmware.eam.security. NotAuthenticated: Failed to authenticate extension com.vmware.vim.eam to vCenter.
com.vmware.eam.security. NotAuthenticated: Failed to authenticate extension com.vmware.vim.eam to vCenter.
com.vmware.eam.security. NotAuthenticated: Failed to authenticate extension com.vmware.vim.eam to vCenter.
com.vmware.eam.security.NotAuthenticated: Failed to authenticate extension com.vmware.vim.eam to vCenter.
com.vmware.eam.security. NotAuthenticated: Failed to authenticate extension com.vmware.vim.eam to vCenter.
com.vmware.eam.security. NotAuthenticated: Failed to authenticate extension com.vmware.vim.eam to vCenter.
Binary file (standard input) matches
[ /var/loq/vmware/eam ]#

The EAM (ESX Agent Manager) extension is missing from vCenter, which can cause the authentication failure.

Resolution

Re-register the EAM extension by following the steps mentioned in the following article Re-register EAM extension to vCenter.

After completing the steps, the EAM extension was successfully re-registered and authenticated with vCenter.

Additionally, NFS mounting issues will be resolved post that.