Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

After enabling vCenter High Availability in a vCenter Server Appliance 6.7 U2, the vmware-certificatemanagement and vmware-topologysvc services fail to start automatically (71117)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 8434Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Recently deployed a vCenter Server Appliance 6.7 U2.

Recently updated from a previous version of 6.7 to vCenter Server Appliance 6.7 U2.

vCenter High Availability is enabled.

After a reboot or fail-over, the vmware-certificatemanagement and vmware-topologysvc services fail to start automatically.

The services can be manually started.

When running the command service-control --status you see entries similar to:

Stopped:
vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-rbd-watchdog vmware-vcha vsan-dps vmware-topologysvc vmware-certificatemanagement
Running:
applmgmt lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-pod vmware-postgres-archiver vmware-rhttpproxy vmware-sca vmware-sps vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-updatemgr vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui

In the /etc/vmware/vmware-vmon/profiles.json file, you see that the certificatemanagement and topologysvc services are missing

{
"NONE" : [],
"HACore" : [ "vcha", "statsmonitor" ],
"HAActive" : [ "rhttpproxy", "sca", "applmgmt", "cis-license", "cm", "content-library", "vpxd-svcs", "eam", "imagebuilder", "mbcs", "netdumper", "perfcharts", "rbd", "sps", "vapi-endpoint", "updatemgr", "vpxd", "vsan-health", "vsm", "vsphere-client", "vmonapi", "vmware-postgres-archiver", "vmcam", "pschealth", "vsphere-ui", "vsan-dps", "analytics"],
"CRITICAL" : ["vpxd", "rhttpproxy", "rbd", "vpxd-svcs", "sps", "vmware-postgres-archiver", "vmware-vpostgres", "vapi-endpoint", "pschealth"]
}

Purpose

To configure the vCenter Server Appliance 6.7 U2 to automatically start the vmware-certificatemanagement and vmware-topologysvc services after a reboot or fail-over.

Cause

In 6.7 U2, the services vmware-certificatemanagement and vmware-topologysvc were introduced.

Out of the box, in a non-VCHA setup, vmware-certificatemanagement and vmware-topologysvc are set to automatically start. However, these services were not correctly added to the HAActive VMON profile.

This means that when VCHA is activated, the VMON profile that determines which services should be running isn't aware that it should also automatically start the vmware-certificatemanagement and vmware-topologysvc services after a reboot or fail-over.

Resolution

This issue is resolved in vCenter Server 6.7 U3, available at VMware Downloads.

Workaround

To work around this issue, follow the steps below:

Disable the VCHA configuration.

Backup the file /etc/vmware/vmware-vmon/profiles.json using the command below:

cp /etc/vmware/vmware-vmon/profiles.json /storage/core/profiles.json;

Edit the /etc/vmware/vmware-vmon/profiles.json file and manually add the certificatemanagement and topologysvc services to the HAActive list.

For example:

{
"NONE" : [],
"HACore" : [ "vcha", "statsmonitor" ],
"HAActive" : [ "rhttpproxy", "sca", "applmgmt", "cis-license", "cm", "content-library", "vpxd-svcs", "eam", "imagebuilder", "mbcs", "netdumper", "perfcharts", "rbd", "sps", "vapi-endpoint", "updatemgr", "vpxd", "vsan-health", "vsm", "vsphere-client", "vmonapi", "vmware-postgres-archiver", "vmcam", "pschealth", "vsphere-ui", "vsan-dps", "analytics", "certificatemanagement", "topologysvc"],
"CRITICAL" : ["vpxd", "rhttpproxy", "rbd", "vpxd-svcs", "sps", "vmware-postgres-archiver", "vmware-vpostgres", "vapi-endpoint", "pschealth"]
}

Note: The service need to be listed as certificatemanagement and topologysvc in the /etc/vmware/vmware-vmon/profiles.json file and not like the names vmware-certificatemanagement and vmware-topologysvc seen in the service-control --status output.

Save the /etc/vmware/vmware-vmon/profiles.json file.

Enable VCHA.

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)

KB
•
「一般システム エラーが発生しました：仮想マシンには、[Domain]system.service.vmware.vsla[Domain] crosshost サービスが必要です (A general system error occurred: The virtual machine requires the [Domain]system.service.vmware.vsla[Domain] crosshost service)」 (71198)

KB
•
如果合作伙伴 PSC 的主机名或 PSC/嵌入式 VC 的 FQDN 为大写字母，则 H5 客户端中不会显示任何复制 (70847)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
在与 vSphere 6.7. x 不兼容的物理主机上托管 vSAN 见证设备 6.7. x (74929)

Results 1-5 of 6

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant