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

"Stopped services: 'topologysvc'" error running a VAMI backup (78734)

Last Updated: 2/9/2021Categories: TroubleshootingTotal Views: 8816Language:
English

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

Note: This KB article specifically addresses an issue with topologysvc service and VAMI Backups. If you experience the same issue with any other service, confirm it is started.

The vCenter Server VAMI Backup fails with error:

Invalid vCenter Server Status: All required services are not up! Stopped services: 'topologysvc'

Manually starting topologysvc fails

Running this command will display multiple registrations for the topologysvc service:

python /usr/lib/vmidentity/tools/scripts/lstool.py list --url https://localhost/lookupservice/sdk --no-check-cert --type topologysvc

Note: Attempting to start the topologysvc service creates a new service registration with Service Type 'topologysvc'

Cause

This issue is caused when the configuration for the Topology Service.is missing when running a VAMI Backup. This results in multiple registrations for the topologysvc service.

Resolution

To resolve the issue, remove duplicate service registrations of Topology Service:

Lists all Topology Service Registrations with this command: python python /usr/lib/vmidentity/tools/scripts/lstool.py list --url https://localhost/lookupservice/sdk --no-check-cert --type topologysvc

Review the results and verify each vCenter Server only has one Topology Service registration:

Name: com.vmware.vcenter.topology.servicenameresource
Description: com.vmware.vcenter.topology.servicedescriptionresource
Service Product: com.vmware.vcenter.topology
Service Type: topologysvc
Service ID: 24c3e3ee-62ac-4944-be9e-1aa39e2673dc
Site ID: default-site
Node ID: c0d1ea69-49d4-45aa-b6cd-6a54588d8d13
Owner ID: [email-masked]
Version: 1.0
Endpoints:
Type: com.vmware.topology.vapi
Protocol: vapi.json.https
URL: https://vcentertest.vmware.com:443/topologysvc
-------------------------------------------------------
Name: com.vmware.vcenter.topology.servicenameresource
Description: com.vmware.vcenter.topology.servicedescriptionresource
Service Product: com.vmware.vcenter.topology
Service Type: topologysvc
Service ID: 6d17e47a-3f32-4857-81d6-6b9ec4a21f11
Site ID: default-site
Node ID: c0d1ea69-49d4-45aa-b6cd-6a54588d8d13
Owner ID: [email-masked]
Version: 1.0
Endpoints:
Type: com.vmware.topology.vapi
Protocol: vapi.json.https
URL: https://vcentertest.vmware.com:443/topologysvc

Un-register duplicate registrations with this command:

/usr/lib/vmidentity/tools/scripts/lstool.py unregister --url https://localhost/lookupservice/sdk --id service_id --user [email-masked]' --password password --no-check-cert

For Example:
/usr/lib/vmidentity/tools/scripts/lstool.py unregister --url https://localhost/lookupservice/sdk --id 6d17e47a-3f32-4857-81d6-6b9ec4a21f11 --user [email-masked]' --password VMware123 --no-check-cert

Open /usr/lib/vmware-topologysvc/config/topologysvc.properties and confirm the entry topologysvc.patch.version=1. If the value is not 1, run this command to change it:

sed -i -e 's/topologysvc.patch.version=0/topologysvc.patch.version=1/g' /usr/lib/vmware-topologysvc/config/topologysvc.properties

Start topologysvc service

service-control --start topologysvc

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
•
登录到链接模式的 vSphere Client 时出现 "500 内部服务器错误" (78653)

KB
•
vCenter Server 6.7 U3 にアップグレードすると vSAN 健全性サービスの起動に失敗する (78921)

KB
•
在 HPE/Hitachi 服务器上使用 HPE 品牌重塑的 Qlogic QLE269x 系列 HBA 时，可能会发生 PSOD 和 VMFS 损坏问题 (76353)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant