免責事項:これは英文の記事 vCenter Server displays alarm: "vc-ws1a-broker status changed from green to unknown" の日本語訳です。記事はベストエフォートで翻訳を進めているため、ローカライズ化コンテンツは最新情報ではない可能性があります。最新情報は英語版の記事で参照してください。
[DATE/TIME] <vCenter_name> vpxd[10740]: Event [85445] [1-1] [DATE/TIME] [vim.event.HealthStatusChangedEvent] [info] [Vmonuser] [] [85445] [vc-ws1a-broker status changed from green to unknown]
[DATE/TIME] <vCenter_name> vpxd[10740]: Event [85446] [1-1] [DATE/TIME] [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']
[DATE/TIME] <vCenter_name> vpxd[10740]: Event [85457] [1-1] [DATE/TIME] [vim.event.HealthStatusChangedEvent] [info] [Vmonuser] [] [85457] [vc-ws1a-broker status changed from unknown to green]
[DATE/TIME] <vCenter_name> vpxd[10740]: Event [85458] [1-1] [DATE/TIME] [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']
さらに、/var/log/vmware/vc-ws1a-broker/nginx-error.log には、以下のようなエラーが含まれています。
[DATE/TIME] [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"
[DATE/TIME] In(05) host-1938 <vc-ws1a-broker-healthcmd> Constructed command: /storage/containers/vc-ws1a-broker/dbb7fed8d494caf9bf2ee657a3622d62b846347019b4e13df5f0bd59128010c0/health_check.sh
[DATE/TIME] Wa(03) host-1938 <vc-ws1a-broker> Service api healthcheck command returned unknown exit code 1
[DATE/TIME] Er(02) host-1938 <vc-ws1a-broker> health state unknown ,considered as system failure
[DATE/TIME] Er(02) host-1938 System Failure, initiating system restart.
vCenter Server 8.0
vc-ws1a-broker コンテナは、ヘルスチェックデータにアクセスする際に、まれに読み取りエラーが発生するため、失敗することがあります。
この問題は vCenter 8.0 Update 3g で解決されました。
vSphere High Availability Issues
PR 3507227: A faulty health status of a microservice under VMware Identity Services might trigger an unexpected vCenter High Availability failover
A false negative health status of a microservice under VMware Identity Services that occurs in very specific conditions might trigger an unexpected vCenter High Availability failover.