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

Skyline collector service stops with the error "No global config found on VAC for deployment ID" (55817)

Last Updated: 7/18/2018Categories: InformationalTotal Views: 2782Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

When logging in as admin to the Collector UI (https://<ip_address_of_collector>), you notice the Collector service is STOPPED

The following symptoms are observed:

After reboot, the service still shows as STOPPED

Starting the service via the Collector UI does not work

Restarting the service via command line does not work

In the /var/log/skyline/collector.log, the following entries are observed:

Couldn't read global config from VAC server, URL string: https://vcsa.vmware.com

No global config found on VAC for deployment ID: skyline_global_configuration. Make sure you haven't changed/deleted this ID in the ConnectionConfig.json

The file /usr/local/skyline/ccf/config/generated/ConnectionConfig.json is present, and has the following value:

"globalConfigDeploymentId" : "skyline_global_configuration",

Solution

This is due to the certificate for https://vcsa.vmware.com not being stored in the Java Keystore for the collector appliance. To confirm the certificate cannot be verified, run the following command:

wget https://vcsa.vmware.com

If the certificate is not verified, you will need to import the certificate for https://vcsa.vmware.com into the JKS.

To download the certificate, run the following command on the collector appliance:

echo -n | openssl s_client -connect vcsa.vmware.com:443 | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > /tmp/myvcsa.cert

Import the certificate created by running the command:

keytool -importcert -file /tmp/myvcsa.cert -keystore /usr/java/jre-vmware/lib/security/cacerts -alias "vcsacert"

When asked for the password, use "changeit" (without the quotations). When asked to trust the certificate, select Yes.

Restart the collector service:

systemctl restart ccf-collector

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
vSphere 用 Intel プロセッサにおける「L1 Terminal Fault」(L1TF - VMM) 投機的実行の脆弱性に対する VMware の対応 CVE-2018-3646 (55806)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Skyline Collector Appliance

Related Versions:

Skyline Collector Appliance 1.x

Take Our Survey

Support Assistant