VMware Cloud Community
Raudi
Expert
Expert

Incorrect service registration found in Lookup Service since update to 7.0.1

Hi,

since upgrade from 7.0d to 7.0.1 have this errors in the vCenter Server Management:

Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:10102/certificateauthority.

Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:10098/topologysvc.

Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:10095/trustmanagement.

Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:7080/tokenservice/vapi.

Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:7080/svcaccountmgmt/vapi.

Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:10096/certificatemanagement.

Failed to connect to 1da6ff8a-0bfd-4605-b4cc-c18ba520e95b\com.vmware.vcenter.nsxd.vapi vAPI provider.

Configuration health status is created between 2020-10-11T16:41:58CEST and 2020-10-11T16:41:58CEST.

For the last one, there is a KB, this can be ignored and for the other errors i searched a little bit.

In the /var/log/vmware/vapi/endpoint/endpoint.log i found this:

Duplicate service URLs detected for URL http://localhost:10102/certificateauthority and serviceIds f4f49eca-389a-4cd4-9539-7b016cd9b387\com.vmware.certificateauthority.vapi and f50da208-1be7-4752-8cda-8651fb94f4bc\com.vmware.certificateauthority.vapi. Service f4f49eca-389a-4cd4-9539-7b016cd9b387\com.vmware.certificateauthority.vapi will not be registered.

Duplicate service URLs detected for URL http://localhost:10098/topologysvc and serviceIds cca05588-4a35-4fb9-aa99-4865202e24db\com.vmware.topology.vapi and 990a4172-d373-43d3-8303-be7cc56b2d64\com.vmware.topology.vapi. Service cca05588-4a35-4fb9-aa99-4865202e24db\com.vmware.topology.vapi will not be registered.

Duplicate service URLs detected for URL http://localhost:10095/trustmanagement and serviceIds b5667b24-3ea2-46eb-a153-37ec8d05c1b5\com.vmware.trustmanagement.vapi and dcaaa1f3-1ac7-4743-be12-37cb748c891e\com.vmware.trustmanagement.vapi. Service b5667b24-3ea2-46eb-a153-37ec8d05c1b5\com.vmware.trustmanagement.vapi will not be registered.

Duplicate service URLs detected for URL http://localhost:7080/tokenservice/vapi and serviceIds 5d3aa82a-a699-4491-8f30-f7914cb8aad6\com.vmware.vcenter.tokenservice.vapi and cef7ec77-cc98-4bd5-81a0-e96d3d142688\com.vmware.vcenter.tokenservice.vapi. Service 5d3aa82a-a699-4491-8f30-f7914cb8aad6\com.vmware.vcenter.tokenservice.vapi will not be registered.

Duplicate service URLs detected for URL http://localhost:7080/svcaccountmgmt/vapi and serviceIds 0e651d0a-db45-4bba-bd1d-7cc40ce831e0\com.vmware.vcenter.svcaccountmgmt.vapi and 07d98dc1-e032-4ab7-b8e2-653985872e69\com.vmware.vcenter.svcaccountmgmt.vapi. Service 0e651d0a-db45-4bba-bd1d-7cc40ce831e0\com.vmware.vcenter.svcaccountmgmt.vapi will not be registered.

Duplicate service URLs detected for URL http://localhost:10096/certificatemanagement and serviceIds adc31b6e-dc7c-4e4f-9a91-d560d6686720\com.vmware.certificatemanagement.vapi and ff27d086-58ac-4215-b672-9ea31f62933d\com.vmware.certificatemanagement.vapi. Service adc31b6e-dc7c-4e4f-9a91-d560d6686720\com.vmware.certificatemanagement.vapi will not be registered.

For a similar problem i at a customer got a command-syntax from the support with "ldapdelete" and with that i deleted the id's which are not registered. after restarting the vapi-endpoint the erros are gone and don't came back.

My question, has someone here a similar problem, how was it solved?

Was my way to delete the not registered ID's correct?

Kind regards

Stefan

Reply
0 Kudos
7 Replies
ashilkrishnan
VMware Employee
VMware Employee

Hi Stefan,

ldapdelete might be one of the options to delete invalid/duplicate service registrations. Another way to remove them is using lstool

List service registrations: /usr/lib/vmware-lookupsvc/tools/lstool.py list --url https://localhost/lookupservice/sdk > /tmp/services.txt

This will list the service name and it's ID. For example:

Service Type: vcenterserver

Service ID: 1dbc3e9f-626d-4314-8731-ca744a0d9f4b

Once you have the service ID, you can run following command to un-register(Update service ID, username and password)

/usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url http://localhost:7080/lookupservice/sdk --id 6ae3bf1a-9318-4a33-b2cb-d2eaa7a306c5 --user 'administrator@vsphere.local' --password 'VMware123!' --no-check-cert 

Raudi
Expert
Expert

Hi,

yes that sounds much easyer than with ldapdelete.

But the service ID i don't need to query, because look in the log i posted. For example:

Duplicate service URLs detected for URL http://localhost:10102/certificateauthority and serviceIds f4f49eca-389a-4cd4-9539-7b016cd9b387\com.vmware.certificateauthority.vapi and f50da208-1be7-4752-8cda-8651fb94f4bc\com.vmware.certificateauthority.vapi. Service f4f49eca-389a-4cd4-9539-7b016cd9b387\com.vmware.certificateauthority.vapi will not be registered.

So i have unregistered the ID which wasn't registered...

I also made a query before, but the services are listed twice, so how should i decide what service id to delete? I decided to follow the log, to delete the not registered service id.

Reply
0 Kudos
Vijay2027
Expert
Expert

You can use lsdoctor with option '--l'

If you do not have external solutions integrated you may try '--r' option

==> https://kb.vmware.com/s/article/80469

Raudi
Expert
Expert

I have the NetApp Virtual Storage Console installed -> VASA Provider for the VVOLs.

So the other solution seems to be the better solution...

But for a small environment with nothing extra this looks simple.

Reply
0 Kudos
Raudi
Expert
Expert

Hi,

and again i have 2 messages in my VCSA:

Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:7080/tokenservice/vapi.
Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:12020/lcm/api.

This time a took a closer look to the tool recommend by @Vijay2027 and so i run: "python ./lsdoctor.py -r"

I used the option 3 to "Replace individual service."

Here i get a list of all services and then i was able to select the "tokenservice", and this was the result:

You have chosen to replace the service: tokenservice -- Continue?[y/n]: y
2021-04-18T09:48:09 INFO unregisterServiceType: Unregistered 607d4ad1-7ac3-49db-a17e-1deb660f4631
2021-04-18T09:48:09 INFO unregisterServiceType: Unregistered cef7ec77-cc98-4bd5-81a0-e96d3d142688
2021-04-18T09:48:09 INFO rebuild_single_service: Registered service: tokenservice with service ID: 607d4ad1-7ac3-49db-a17e-1deb660f4631

2 services unregistered and one is registered, perfect. The same with the other service:

You have chosen to replace the service: cis.vlcm -- Continue?[y/n]: y
2021-04-18T09:49:29 INFO unregisterServiceType: Unregistered e5df686b-7cdb-4de2-9ac5-927bd6e481ec
2021-04-18T09:49:29 INFO unregisterServiceType: Unregistered 9a29af6f-22ea-473e-905d-131b1aee6104
2021-04-18T09:49:29 INFO rebuild_single_service: Registered service: cis.vlcm with service ID: 7a7f5b32-ed67-4778-bb25-4c077ef0f67e

So this is the best and safe way to solve that problem. And i think even if i have external solutions integrated it must work, because i don't "rebuild" all services, i rebuild only the selected service.

And after a few minutes the messages in the VCSA services is gone.

The other way, suggested by @ashilkrishnan, here is the problem, how can i decide which of the two registrations is the correct one? This is more complex...

So thank you, @Vijay2027 for the link to the KB!

Kind regards
Stefan

Raudi
Expert
Expert

Very strange, yesterday i installed a vCenter Patch and today again:

Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:12020/lcm/api.

But only this one...

Now i must wait for a new version of the lsdoctor, when there is a template for 7.0.2.00100 included...

Reply
0 Kudos
TRobinsonSig
Contributor
Contributor

Thanks for this.  Solved my variant of this issue.  I opted for replacing individual service and picked my service. 

option 3. Replace individual service.
picked appropriate file
picked appropriate service (18 - trustmanagement in my case)

Rebooted and all was well.

Reply
0 Kudos