OPERATIONAL DEFECT DATABASE
...
...
While upgrading VCSA 6.0 to 6.x, getting error message: An error occurred while starting service 'pschealth' In firstbootInfrastructure.log file, you will see entries similar to: 2017-05-16T16:11:18.377Z INFO firstbootInfrastructure [Finished] /usr/lib/vmware-netdumper/firstboot/netdump-firstboot.py is complete2017-05-16T16:11:18.379Z INFO firstbootInfrastructure Running firstboot script: ['/opt/vmware/bin/python', '/usr/lib/vmware-pschealth/firstboot/pschealth-firstboot.py', '--action', 'firstboot', '--compkey', u'pschealth', '--errlog', u'/var/log/firstboot/pschealth-firstboot.py_7866_stderr.log']2017-05-16T16:12:18.25Z INFO firstbootInfrastructure [Failed] /usr/lib/vmware-pschealth/firstboot/pschealth-firstboot.py is complete2017-05-16T16:12:18.27Z WARNING firstbootInfrastructure Bug component info file does not exist2017-05-16T16:12:18.27Z INFO firstbootInfrastructure Firstboot duration: -254 sec2017-05-16T16:12:18.27Z INFO firstbootInfrastructure First boot is a failure2017-05-16T16:12:18.009Z ERROR starting pschealth rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting2017-05-16 16:12:18,009 ERROR 119 PSCHealth Firstboot failed2017-05-16 16:12:18,011 ERROR 120 Exception: Traceback (most recent call last):File "/usr/lib/vmware-pschealth/firstboot/pschealth-firstboot.py", line 105, in main pschealthFB.firstbootAction()File "/usr/lib/vmware-pschealth/firstboot/pschealth-firstboot.py", line 74, in firstbootAction self.startService()File "/usr/lib/vmware-pschealth/firstboot/pschealth-firstboot.py", line 63, in startService self.start_service()File "/usr/lib/vmware/site-packages/cis/firstboot.py", line 272, in start_service service_start(self.get_eff_service_name())File "/usr/lib/vmware/site-packages/cis/utils.py", line 742, in service_start raise ServiceStartException(svc_name)ServiceStartException: {"resolution": null,"detail": [{"args": ["pschealth"], "id": "install.ciscommon.service.failstart", "localized": "An error occurred while starting service 'pschealth'", "translatable": "An error occurred while starting service '%(0)s'"}],"componentKey": null, "problemId": null}PSChealth service not starting seems to be just a symptom. Some of the PSC service is not responding and health monitor exits.2017-05-16T16:11:18.756354+00:00 usvcentervsandr pschealthd: starting pschealthd2017-05-16T16:11:18.762316+00:00 usvcentervsandr pschealthd: Detected vmafd is starting up wait for 1 min2017-05-16T16:12:18.004665+00:00 usvcentervsandr pschealthd: VMware Directory-Service, 0, 1572017-05-16T16:12:18.005105+00:00 usvcentervsandr pschealthd: VMware Certificate-Service, 0, 1512017-05-16T16:12:18.005348+00:00 usvcentervsandr pschealthd: IdentityManager, 0, 1542017-05-16T16:12:18.005593+00:00 usvcentervsandr pschealthd: Websso, 0, 1592017-05-16T16:12:18.005817+00:00 usvcentervsandr pschealthd: Lookup service, 0, 1572017-05-16T16:12:18.006045+00:00 usvcentervsandr pschealthd: Security Token Service, 0, 1562017-05-16T16:12:18.006286+00:00 usvcentervsandr pschealthd: License Service, 0, 3312017-05-16T16:12:18.006509+00:00 usvcentervsandr pschealthd: Admin, 0, 1522017-05-16T16:12:18.006746+00:00 usvcentervsandr pschealthd: Detected PSC system not healthy exiting2017-05-16T16:19:26.570953+00:00 localhost systemd[1]: Configuration file /usr/lib/systemd/system/getty@tty2.service.d/dcui_override.conf is marked world-writable. Please remove world writability permission bits. Proceeding anyway.2017-05-16T16:09:46.950222+00:00 localhost systemd[1]: Time has been changed2017-05-16T16:09:51.400270+00:00 localhost systemd[1]: Reloading.
To resolve this issue, set the host and vCenter Server to the same time. There should be no time difference between them.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
