Duplicate entries found for the "service type: vsphere.client"

Products

• VMware vCenter Server

Issue/Introduction

• This article guides the removal of stale service IDs from the vCenter Server through an SSH session.
  
  
• The VDT tool reports an SSO check failure with the following error: “Duplicates found. You must unregister the extra endpoints.”
  
• Steps to check stale registrations on vCenter Server:
  -- List of the services registered within the vCenter:
      /usr/lib/vmware-lookupsvc/tools/lstool.py list --url https://localhost/lookupservice/sdk --no-check-cert > /tmp/psc.txt
  
  -- Validate the number of service registrations for each vCenter:
    less /tmp/psc.txt | grep -i "Service Type: " | sort | uniq -c
  
  Below is the output for the above command.
  

Environment

VMware vCenter Server 8.x

Resolution

To remove the stale entries identified, follow the steps below

• Take a snapshot without memory of the vCenter Server if it is a standalone instance, or powered-off snapshots of all vCenter Servers if they are in Linked Mode.
  
  
• If vCenter is configured with VCHA, please place VCHA under maintenance. Refer to the following document for guidance.
  Edit the vCenter HA Cluster Configuration
  
  
• The firstboot log contains all service registration entries downloaded during the vCenter Server installation. From this log, you can identify the valid Service ID that was originally registered on the vCenter Server.
  
  
• Navigate to the directory /var/log/firstboot on the vCenter Server and run the command below to locate the Service ID for which a duplicate entry is detected:
  grep -i "Service ID" * | less


• If you receive an output similar to the one shown below for the Service ID, it indicates that the Service ID is currently installed on the vCenter Server and is valid. Therefore, it should not be removed.
  root@vcenter03 [/var/log/firstboot]# grep -i "d582####-####-####-####-149########" * | less
vsphere_ui_firstboot.py_22101_stdout.log:2020-07-27T05:19:52.469Z  Service ID=d582####-####-####-####-149########
vsphere_ui_firstboot.py_22101_stdout.log:2020-07-27T05:19:52.767Z  Successfully performed tryupgrade operation for service d582####-####-####-####-149########


• Access the vCenter Server via SSH and run the command below to unregister the stale Service ID.
  /usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url http://localhost:7090/lookupservice/sdk --id <Stale_Service_ID> --user 'administrator@sso_domain' --password 'sso_password' --no-check-cert
Note: Replace <Stale_Service_ID> with the UUID.
  
  
• Restart the services using the command below.
  service-control --stop --all && service-control --start --all

Additional Information

Reference Articles:
Script to remove stale service registrations from vCenter Server.
Possible duplicate entries in the Lookup Service Registration Database detected.

 

If the above steps in this KB do not resolve the issue, raise a support ticket with Broadcom support, selecting vCenter as the product. 
Handling Log Bundles for offline review with Broadcom support.
Uploading files to cases on the Broadcom Support Portal
Creating and managing Broadcom support cases