'PSC Service Health Alarm' on the vCenter
search cancel

'PSC Service Health Alarm' on the vCenter

book

Article ID: 344814

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • PSCHealth status changes from green to red in the vCenter alarm 
  • Similar entries in /var/log/vmware/messages: 

    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: #####]
  • In Vmon-syslog.log, you see messages similar to: 
    18-01-31T12:00:29.022933+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 49. Taking configured recovery action.
18-01-31T13:05:08.017811+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 50. Taking configured recovery action.
18-01-31T13:21:59.028480+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 51. Taking configured recovery action.
18-01-31T14:20:02.004136+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 52. Taking configured recovery action.
18-01-31T15:02:33.022028+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 53. Taking configured recovery action.
18-01-31T15:53:34.024437+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 54. Taking configured recovery action.
18-01-31T16:17:57.019621+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 55. Taking configured recovery action.
18-01-31T16:33:35.028512+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 56. Taking configured recovery action.
18-01-31T16:53:43.017070+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 57. Taking configured recovery action.
18-01-31T17:09:36.028041+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 58. Taking configured recovery action.

Environment

VMware vCenter Server 6.0.x

VMware vCenter Server 7.0.x

VMware vCenter Server 8.0.x

Cause

This issue occurs if there is a time sync problem in vCenter Server.

Resolution

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

Powered by Wolken Software