pschealth status changed from green to red
search cancel

pschealth status changed from green to red

book

Article ID: 336248

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • pschealth status changes from green to red
  • In Vmon-syslog.log, you see messages similar to:
 
8-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.
 
 
18-01-31T05:11:34.029700+00:00 warning vmon  Service pschealth exited. Exit code 1
18-01-31T05:11:34.029945+00:00 warning vmon  Service pschealth exited unexpectedly. Crash count 39. Taking configured recovery action.
18-01-31T05:11:34.030274+00:00 notice vmon  Restarting service pschealth
18-01-31T05:11:34.030452+00:00 notice vmon  Constructed command: /usr/lib/vmware-pschealth/sbin/pschealthd -s
18-01-31T05:11:34.030610+00:00 notice vmon  Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonEventPublisher.py --eventdata pschealth,UNHEALTHY,HEALTHY,1
18-01-31T05:11:34.652094+00:00 notice vmon  Successfully published health status change.


In the Messages.log, you see message similar to:
 
2018-01-31T13:20:49.726438+00:00 vc1 systemd[1]: Time has been changed
2018-01-31T13:24:46.013721+00:00 vc1 systemd[1]: Time has been changed
2018-01-31T13:24:46.014042+00:00 vc1 lsassd[1151]: 0x7f36e0b90700:Failed to sync system time [error code: 40075]
2018-01-31T13:37:39.078485+00:00 vc1 systemd[1]: Time has been changed
2018-01-31T13:40:54.000986+00:00 vc1 systemd[1]: Time has been changed
2018-01-31T13:40:54.001892+00:00 vc1 lsassd[1151]: 0x7f36e0b90700:Failed to sync system time [error code: 40075]
2018-01-31T13:56:37.496135+00:00 vc1 systemd[1]: Time has been changed
2018-01-31T14:02:02.009574+00:00 vc1 systemd[1]: Time has been changed
2018-01-31T14:02:02.009915+00:00 vc1 lsassd[1151]: 0x7f36e0b90700:Failed to sync system time [error code: 40075]
2018-01-31T14:18:49.969083+00:00 vc1 systemd[1]: Time has been changed
2018-01-31T14:23:10.012850+00:00 vc1 systemd[1]: Time has been changed
2018-01-31T14:23:10.013231+00:00 vc1 lsassd[1151]: 0x7f36e0b90700:Failed to sync system time [error code: 40075]
2018-01-31T14:37:58.376191+00:00 vc1 systemd[1]: Time has been changed
2018-01-31T14:44:18.002584+00:00 vc1 lsassd[1151]: 0x7f36e0b90700:Failed to sync system time [error code: 40075]
2018-01-31T14:44:18.002866+00:00 vc1 systemd[1]: Time has been changed

 

Environment

VMware vCenter Server 6.0.x

Cause

This issue occur if there is a time sync between the PSC and vCenter Server or vCenter Server and host.

Resolution

To Resolve the issue:

Ensure that the vCenter Server can sync the time with host.
Or
Update the time manually between PSC and vCenter Server