'Analytics Service registration with Component Manager failed', 'ns0:MessageExpired' firstboot error while upgrading VCSA 6.7
Article ID: 338178
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Symptoms:
To learn more about firstboot issues see: Understanding and Troubleshooting vCenter Server and vCenter Server Appliance 6.7 Firstboot Install/Deployment, Upgrade, or Migration Failures.
To collect a log bundle or review log files for a vCenter Server Appliance install, upgrade, or migration issues reference Triaging a vCenter Server Appliance 6.0 installation, upgrade, or migration (6.0 U2m) failure. The relevant logs will be on the newly deployed appliance.
firstbootStatus.json contains the following:
"failedSteps": "analytics_firstboot"
analytics_firstboot.py_####_stderr.log contains the following:
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.
Note:
To learn more about firstboot issues see: Understanding and Troubleshooting vCenter Server and vCenter Server Appliance 6.7 Firstboot Install/Deployment, Upgrade, or Migration Failures.
To collect a log bundle or review log files for a vCenter Server Appliance install, upgrade, or migration issues reference Triaging a vCenter Server Appliance 6.0 installation, upgrade, or migration (6.0 U2m) failure. The relevant logs will be on the newly deployed appliance.
firstbootStatus.json contains the following:
"failedSteps": "analytics_firstboot"
analytics_firstboot.py_####_stderr.log contains the following:
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.
Note:
- vCenter Server Appliance - Firstboot logs are located in the /var/log/firstboot directory.
Environment
VMware vCenter Server Appliance 6.7.x
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:
For more information on changing DRS Automation, see Edit Cluster Settings.
For more information on vCenter Server Appliance requirements, see System Requirements for the vCenter Server Appliance and Platform Services Controller 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 changing DRS Automation, see Edit Cluster Settings.
For more information on vCenter Server Appliance requirements, see System Requirements for the vCenter Server Appliance and Platform Services Controller Appliance.
Feedback
Yes
No
Powered by
