vSAN Health Service -- vSAN File Service Infrastructure Health -- Root files system not responsive on host

Products

• VMware vSAN

Issue/Introduction

vSAN Health Service -- vSAN File Service Infrastructure Health -- Root files system not responsive on host  

Clicking "Remediate File Service" doesn't resolve the issue and now the alert is also reporting that the "Sockrelay is not running".

From the vdfsd-proxy.log of the impacted host we see the following messages:

2025-10-16T21:15:35.171Z|m-0----------|VDFSSKT: No(29) vdfsd-proxy[2976007] readErr: fd=62 -- AsyncSocketException: socket closing after error (peer=172.##.##.102:1564, local=172.##.##.101:14341), type = Internal error -- Failure
2025-10-16T21:15:35.171Z|f-0-000000009|VDFSSKT: Er(27) vdfsd-proxy[2976007] TLSConnect: sslConn failed: Failure (195887105)
2025-10-16T21:15:35.171Z|f-0-000000009|PROXY: Er(27) vdfsd-proxy[2976007] 48a46d68-5aca-c81b-a747-1423f20869fc conn-0: TLS handshake with server 172.##.##.102 failed: Failure
2025-10-16T21:15:35.171Z|f-0-000000009|PROXY: Er(27) vdfsd-proxy[2976007] 48a46d68-5aca-c81b-a747-1423f20869fc conn-0: client: 127.0.0.1 fd=58 server: 172.##.##.102 fd=62 -- state: 1 FAILED: Failure
2025-10-16T21:15:35.171Z|f-0-000000009|PROXY: No(29) vdfsd-proxy[2976007] 48a46d68-5aca-c81b-a747-1423f20869fc conn-0: 172.##.##.102 fd=62: closing conn
2025-10-16T21:15:35.171Z|f-0-000000009|VDFSSKT: No(29) vdfsd-proxy[2976007] fd=62 (mgr=0) -- closing
2025-10-16T21:15:35.171Z|f-0-000001986|PROXY: Er(27) vdfsd-proxy[2976007] 48a46d68-5aca-c81b-a747-1423f20869fc conn-0: 172.##.##.102 fd=62: server error: Failure

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vSAN (All Versions)

vSAN File Services

Cause

The vdfsd-proxy and sockrely services are in a restart loop due to a bad host cert on the host.

Resolution

Renew the host certificate