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

vCenter Cloud Gateway Deployment Fails during Firstboot while Starting VMware Analytics Service (57241)

Last Updated: 8/4/2018Categories: TroubleshootingTotal Views: 4245Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The vCenter Cloud Gateway Appliance fails to deploy and gives the following error:

===========================================
Task: Run firstboot scripts.(FAILED 35/100) - Starting VMware Analytics Service...
Error: Analytics Service registration with Component Manager failed.
Resolution: Please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.

Cause

This is issue should be further investigated in the analytics_firstboot.py_xxxx_stderr.log file. In the log file may find the below log snips:

===================================
INFO:root:Register service with LS.
2018-08-03T17:38:13.271Z  Failed to register Analytics Service with Component Manager: SoapException:
faultcode: ns0:InvalidTimeRange
faultstring: The token authority rejected an issue request for TimePeriod [startTime=Fri Aug 03 17:38:13 UTC 2018, endTime=Fri Aug 03 17:40:13 UTC 2018] :: The requested token start time differs from the issue instant more than the acceptable deviation (clock tolerance) of 600000 ms. Requested token start time=Fri Aug 03 17:38:13 UTC 2018, issue instant time=Fri Aug 03 17:48:42 UTC 2018. This might be due to a clock skew problem.
faultxml: <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode xmlns:ns0="http://docs.oasis-open.org/ws-sx/ws-trust/200512">ns0:InvalidTimeRange</faultcode><faultstring>The token authority rejected an issue request for TimePeriod [startTime=Fri Aug 03 17:38:13 UTC 2018, endTime=Fri Aug 03 17:40:13 UTC 2018] :: The requested token start time differs from the issue instant more than the acceptable deviation (clock tolerance) of 600000 ms. Requested token start time=Fri Aug 03 17:38:13 UTC 2018, issue instant time=Fri Aug 03 17:48:42 UTC 2018. This might be due to a clock skew problem.</faultstring></S:Fault></S:Body></S:Envelope>
2018-08-03T17:38:13.274Z  Traceback (most recent call last):
File "/usr/lib/vmware-analytics/firstboot/analytics_firstboot.py", line 161, in register_with_cm
cloudvm_sso_cm_register(keystore, cisreg_spec, key_alias, dyn_vars, isPatch=is_patch)
File "/usr/lib/vmware-cm/bin/cloudvmcisreg.py", line 700, in cloudvm_sso_cm_register
serviceId = do_lsauthz_operation(cisreg_opts_dict)
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 1064, in do_lsauthz_operation
ls_obj.register_service(svc_id, svc_create_spec)
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 340, in add_securityctx_to_requests
with self._sso_client.securityctx_modifier(self._stub):
File "/usr/lib/python3.5/contextlib.py", line 59, in __enter__
return next(self.gen)
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 240, in securityctx_modifier
self._update_saml_token()
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 223, in _update_saml_token
self._uname, self._passwd, token_duration=120)
File "/usr/lib/vmware/site-packages/pyVim/sso.py", line 319, in get_bearer_saml_assertion
ssl_context)
File "/usr/lib/vmware/site-packages/pyVim/sso.py", line 258, in perform_request
raise SoapException(fault, *parsed_fault)
pyVim.sso.SoapException: SoapException:
===================================

The above log snip shows that there is a time skew between ESXi Hosts / vCenter / SSO components that are causing the SAML Tokens to expire prior to being used which causes a failure to authenticate ultimately leading to the deployment failure.

Resolution

To resolve the issue, ensure that all ESXi hosts and vCenter components are configured to use NTP for synchronized time between all components.

Once all components are configured with NTP, deploy the vCenter Cloud Gateway again.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant