Symptoms:
- 'PSC Service Health Alarm' is triggered in the vCenter HTML5 Client, and re-triggers if reset to green.
- There are similar entries in /var/log/vmware/messages to those found in the example below:0000-00-00T00:00:00.000000+00:00 VCSA lsassd[#####]: #x############:Failed to sync system time [error code: #####]
0000-00-00T00:00:00.000000+00:00 VCSA systemd[1]: Time has been changed
0000-00-00T00:00:00.000000+00:00 VCSA CROND[#####]: (root) CMD ( /usr/sbin/iiad.sh >/dev/null 2>&1)
0000-00-00T00:00:00.000000+00:00 VCSA cli: twisted "127.0.0.1" - - [##/Jan/####:##:##:## +####] "POST /api HTTP/1.1" ### #### "-" "vAPI http client"
0000-00-00T00:00:00.000000+00:00 VCSA systemd[1]: Time has been changed
0000-00-00T00:00:00.000000+00:00 VCSA systemd[1]: Time has been changed
0000-00-00T00:00:00.000000+00:00 VCSA lsassd[#####]: #x############:Failed to sync system time [error code: #####]
0000-00-00T00:00:00.000000+00:00 VCSA CROND[#####]: (root) CMD ( test -x /usr/sbin/cloudvm_ram_size_periodic && /usr/sbin/cloudvm_ram_size_periodic >/dev/null 2>&1)
0000-00-00T00:00:00.000000+00:00 VCSA CROND[#####]: (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)
0000-00-00T00:00:00.000000+00:00 VCSA CROND[#####]: (root) CMD ( /usr/sbin/iiad.sh >/dev/null 2>&1)
0000-00-00T00:00:00.000000+00:00 VCSA cli: twisted "127.0.0.1" - - [##/Jan/####:##:##:## +####] "POST /api HTTP/1.1" ### #### "-" "vAPI http client"
0000-00-00T00:00:00.000000+00:00 VCSA netlogond[#####]: #x############: Failed ldap search on ###.###.###.### error=#####
0000-00-00T00:00:00.000000+00:00 VCSA cli: twisted "127.0.0.1" - - [##/Jan/####:##:##:## +####] "POST /api HTTP/1.1" ### #### "-" "vAPI http client"
0000-00-00T00:00:00.000000+00:00 VCSA CROND[#####]: (root) CMD ( /usr/sbin/iiad.sh >/dev/null 2>&1)
0000-00-00T00:00:00.000000+00:00 VCSA systemd[1]: Time has been changed
0000-00-00T00:00:00.000000+00:00 VCSA lsassd[#####]: #x############:Failed to sync system time [error code: #####]
0000-00-00T00:00:00.000000+00:00 VCSA systemd[1]: Time has been changed
0000-00-00T00:00:00.000000+00:00 VCSA cli: twisted "127.0.0.1" - - [##/Jan/####:##:##:## +####] "POST /api HTTP/1.1" ### #### "-" "vAPI http client"
0000-00-00T00:00:00.000000+00:00 VCSA CROND[#####]: (root) CMD ( test -x /usr/sbin/cloudvm_ram_size_periodic && /usr/sbin/cloudvm_ram_size_periodic >/dev/null 2>&1)
0000-00-00T00:00:00.000000+00:00 VCSA CROND[#####]: (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)
0000-00-00T00:00:00.000000+00:00 VCSA CROND[#####]: (root) CMD ( /usr/sbin/iiad.sh >/dev/null 2>&1)
0000-00-00T00:00:00.000000+00:00 VCSA cli: twisted "127.0.0.1" - - [##/Jan/####:##:##:## +####] "POST /api HTTP/1.1" ### #### "-" "vAPI http client"
0000-00-00T00:00:00.000000+00:00 VCSA systemd[1]: Time has been changed
0000-00-00T00:00:00.000000+00:00 VCSA systemd[1]: Time has been changed
0000-00-00T00:00:00.000000+00:00 VCSA lsassd[#####]: #x############:Failed to sync system time [error code: #####]
VMware vCenter Server 6.X, 7.X, 8.X
The alert can be cleared by configuring the vCenter Appliance Time Synchronization to sync with NTP servers or with the ESXi host.
NOTE: If syncing the vCenter time with an ESXi host, the host should be configured to sync time with an external NTP.
See the following documentation for configuring NTP within a vCenter Server/Appliance and ESXi host.
Configure the System Time Zone and Time Synchronization Settings
Configuring Time Synchronization Settings in vCenter Server
Configure Network Time Protocol (NTP) for ESXi