journalctl -b 0
" the following events can be seen:
Apr 02 18:11:44 <vCenter_name> vpxd[10740]: Event [85445] [1-1] [2025-04-02T18:11:44.187012Z] [vim.event.HealthStatusChangedEvent] [info] [Vmonuser] [] [85445] [vc-ws1a-broker status changed from green to unknown]
Apr 02 18:11:44 <vCenter_name> vpxd[10740]: Event [85446] [1-1] [2025-04-02T18:11:44.193412Z] [vim.event.EventEx] [info] [] [] [85446] [Alarm 'Health status changed alarm' on Datacenters triggered by event 85445 'vc-ws1a-broker status changed from green to unknown']
Apr 02 18:16:50 <vCenter_name> vpxd[10740]: Event [85457] [1-1] [2025-04-02T18:16:50.570414Z] [vim.event.HealthStatusChangedEvent] [info] [Vmonuser] [] [85457] [vc-ws1a-broker status changed from unknown to green]
Apr 02 18:16:50 <vCenter_name> vpxd[10740]: Event [85458] [1-1] [2025-04-02T18:16:50.571736Z] [vim.event.EventEx] [info] [] [] [85458] [Alarm 'Health status changed alarm' on Datacenters triggered by event 85457 'vc-ws1a-broker status changed from unknown to green']
2025/04/02 18:11:42 [alert] 67#0: *1874 pread() read only 0 of 5 from "/opt/vmware/idm/health/healthCheck" while sending response to client, client: ::ffff:127.0.0.1, server: localhost, request: "GET /sddc/broker/health HTTP/1.1", host: "localhost:10121"
vCenter Server 8.0
The vc-ws1a-broker container may rarely fail due to a read error when accessing health check data.
This is a benign and transient issue.
There is no functional impact on vCenter Server operations.