"Stopped services: 'topologysvc'" error running a VAMI backup
search cancel

"Stopped services: 'topologysvc'" error running a VAMI backup

book

Article ID: 338246

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

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'

Environment

VMware vCenter Server Appliance 6.7.x

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:

  1. 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
  2. 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-####-####-####-########3dc
Site ID: default-site
Node ID: c0d1ea69-####-####-####-########d13
Owner ID: machine-9060afc0-####-####-####-########[email protected]
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-####-####-####-########f11
Site ID: default-site
Node ID: c0d1ea69-####-####-####-########d13
Owner ID: machine-9060afc0-####-####-####-########[email protected]
Version: 1.0
Endpoints:
        Type: com.vmware.topology.vapi
        Protocol: vapi.json.https
        URL: https://vcentertest.vmware.com:443/topologysvc
  1. 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 protected]' --password password --no-check-cert

For Example:
/usr/lib/vmidentity/tools/scripts/lstool.py unregister --url https://localhost/lookupservice/sdk --id 6d17e47a-####-####-####-########f11 --user '[email protected]' --password VMware123 --no-check-cert
  1. 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
  1. Start topologysvc service
service-control --start topologysvc