Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Firstboot fails when upgrading vCenter Server Appliance 6.7 and vCenter Server 7.x due to time synchronization issue (57085)

Last Updated: 4/2/2020Categories: TroubleshootingTotal Views: 47265Language:
Chinese (Simplified)JapaneseEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

The components of the vSphere environment are not time synchronized.

Firstboot fails during Install/Deployment, Upgrade or Migration.

In the firstbootStatus.json file, you may see one of these services have failed to configure or start during firstboot:

"failedSteps": "cmfirstboot"

"failedSteps": "analytics_firstboot"

"failedSteps": "vpxd_firstboot"

"failedSteps": "pschealth-firstboot”

"failedSteps": "sms_spbm_firstboot"

"failedSteps": "vmafd-firstboot"

"failedSteps": "vapi_firstboot"

"failedSteps": "mgmt-firstboot"

"failedSteps": "scafirstboot"

"failedSteps": "updatemgr-firstboot"

"failedSteps": "ngc_firstboot"

In the cmfirstboot.py_####_stderr.log file, you see the error:

PAM: Authentication token is no longer valid

An error occurred while performing security operation: 'Failed to add user: cm to group: cis’

In the analytics_firstboot.py_####_stderr.log file, you see the error:

Analytics Service registration with Component Manager failed
ns0:MessageExpired
The time now (date + time) does not fall in the request lifetime interval extended with clock tolerance of 600000 ms [ (date + time); (date +time)]. This might be due to a clock skew problem.

In the vpxd_firstboot.py_####_stdout.log file, you see the error:

ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)

In the pschealth-firstboot.py_#####_stderr.log file, you see the error:

An error occurred while starting service 'pschealth'

In the sms_spbm_firstboot.py_####_stderr.log file, you see the error:

VMware vSphere Profile-Driven Storage Service failed to start

In the vmafdd-syslog.log file, you see the error:

Vmdir server is down.

In the vmdird-syslog.log file, you see the error:

DecodeEntry failed (9605) DN:()

LoadServerGlobals: (9700)()

In the vapi_firstboot.py_####_stderr.log file, you see the error:

Failed to configure vAPI Endpoint Service at the firstboot time

In the mgmt-firstboot.py_####_stderr.log file, you see the error:

UnboundLocalError: local variable 'e' referenced before assignment

In the scafirstboot.py_####_stderr.log file, you see the error:

[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)

In the updatemgr-firstboot.py_6012_stderr.log file, you see the error:

Failed to register updatemgr extension

In the ngc_firstboot.py_####_stderr.log file, you see the error:

SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:720)

In the %ProgramData%\VMware\vCenterServer\logs\cm\cm.log file, you see entries similar to:

Caused by: com.vmware.vim.vmomi.client.exception.VlsiCertificateException: Server certificate chain is not trusted and thumbprint verification is not configured
at com.vmware.vim.vmomi.client.http.impl.ThumbprintTrustManager.checkServerTrusted(ThumbprintTrustManager.java:183)
at sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:984)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1496)
... 78 more
Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed

In the fbInstall.json file shows an unexpected time discrepancy between the start time and end time. This could be a large jump forward or backward in time.

For example:

"start_time": "2018-05-07T13:00:00.000Z
"end_time": "2018-05-07T18:00:00.000Z"

or

"start_time": "2018-05-07T18:05:00.000Z
"end_time": "2018-05-07T18:00:00.000Z"

Cause

This issue occurs due to time inconsistencies in the vSphere environment.  The issue most commonly happens when the target ESXi host for the destination vCenter Server Appliance is not synchronized with NTP.  This issue can also happen if the destination vCenter Server Appliance migrates to an ESXi host with different time due to fully automated DRS.

Resolution

To avoid time synchronization issues, ensure the following is correct before deploying, migrating, or upgrading a vCenter Server Appliance:

The target ESXi host where the destination vCenter Server Appliance will be deployed is synchronized to NTP.

If the target ESXi host is part of a Fully Automated DRS cluster, change the automation level to Manual.

The ESXi host running the source vCenter Server Appliance is synchronized to NTP.

If the vCenter Server Appliance will be connected to an external Platform Services Controller, ensure the ESXi host running the external Platform Services Controller is synchronized to NTP.

Verify that the source vCenter Server or vCenter Server Appliance and external Platform Services Controller have the correct time.

For more information on:

Managing time in vSphere, see Synchronizing Clocks on the vSphere Network.

Changing DRS Automation, see Edit Cluster Settings.

vCenter Server Appliance requirements, see System Requirements for the vCenter Server Appliance and Platform Services Controller Appliance.

Related Information

Note: Firstboot logs are located at:

vCenter Server Appliance - Firstboot logs are located in the /var/log/firstboot directory.

vCenter Server on Windows - Firstboot logs are located in the VMware-VCS-logs-.zip/vcs_logs/uninstall directory

or

VMware-VCS-logs-/vcs_logs/uninstall/.zip/ProgramData/VMware/vCenterServer/logs/firstboot directory

Note: In vSphere 7.0, vCenter Server for Windows has been removed and support is not available. For more information, see Farewell, vCenter Server for Windows .

To collect a log bundle or review log files:

Triaging a vCenter Server Appliance 6.0 installation, upgrade, or migration (6.0 U2m) failure (2106760)

Triaging a vCenter Server 6.0 installation or upgrade failure (2105258)

For more information, see VMware vCenter Failed Firstboot.

-------------------------------------------------------------------------------------------------------------------------------------------------
For more information see:

Error - An error occurred while starting service 'pschealth' 

Synchronizing ESXi/ESX time with a Microsoft Domain Controller

"Newly deployed vCenter Server Appliance time is not synchronized with Platform Services Controller" while deploying vCenter from 6.x to 6.7 fails at Pre-Migration check

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
VMware End Of Availability of Perpetual Licensing and SaaS Services (96168)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant