VMware Cloud Community
Shylidi
Contributor
Contributor

Duplicate instance of VMware Cloud Director Availability

I'm running a Homelab with three hosts, but I've got one warning on my vCenter Appliance instance I cannot resolve. I have a duplicate, older version of a client plugin and it attempts to download it over and over. Anyone have a lead on a fix, 4 hours of google and forum reading have led to nothing.

I've attached a screenshot of the Client Plug in list, with the client id's enabled, showing two, one version 0.4.0.0 and 0.4.1.0. The second works fine, the first is broken and I believe I need to remove it...

For reference I have attempted to go to mob and used content>extension manager>unregister extension with no luck.

I apologize if this is the wrong area to post, but any help would be greatly appreciated. Thanks.

Reply
0 Kudos
33 Replies
scott28tt
VMware Employee
VMware Employee

@Shylidi 

Moderator: Moved to vCenter Server Discussions


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
Reply
0 Kudos
bryanvaneeden
Hot Shot
Hot Shot

Hi @Shylidi ,

My first try would be to use the mob browser to list and remove the extension. It seems that you already did this. I am wondering what message the mob browser showed you once you did this, and if the extension is still listed in the mob browser?

If not, you might want to restart the vCenter Server (maybe you already tried this).

Next up, I would have a look at the vCenter vSphere Client (UI) logs to check what is happening with this extension. These logs should yield some information honestly. The logs I am mentioning are located in the following locations:

/var/log/vmware/vsphere-client
/var/log/vmware/vsphere-ui

Please let me know what you can find.

Visit my blog at https://vcloudvision.com!
Shylidi
Contributor
Contributor

okay, I'm looking at the bash directory for client-ui, and I'm unsure where I should look:

 

 

Reply
0 Kudos
Shylidi
Contributor
Contributor

This is the output of the extension manager:

Reply
0 Kudos
bryanvaneeden
Hot Shot
Hot Shot

Hi @Shylidi ,

You should look at all of them, but you can start with:

  • eventlog.log
  • dataservice.log
  • vsphere_client_virgo.log
  • catalina.log
  • host-manager.log

As far as the extension goes, I have the following extension on my vCenter Server that has the VCDA plugin installed: com.vmware.h4.vsphere.client

But, this extension is not visible in my mob browser, like in yours. This should be normal behaviour I guess (weird though). I however have version: 4.0.1.1252999

What version of VCDA are you running? If at all possible, I would suggest to turn of the VCDA feature in vCenter (if vCenter 7) or de-register the VCDA On-Premise appliance from the vCenter (if vCenter 6.7) to completely de-couple it from the vCenter Server and re-join it.

 
Visit my blog at https://vcloudvision.com!
Shylidi
Contributor
Contributor

I do not need VCDA, and I am running vSphere 7

How would I go about disabling it?

Reply
0 Kudos
bryanvaneeden
Hot Shot
Hot Shot

Ok, well disable the VCDA plugin in the Client Plugin window.

Visit my blog at https://vcloudvision.com!
Reply
0 Kudos
Shylidi
Contributor
Contributor

Unfortunately it does not appear as a service in the vCenter Server. But in vSphere Client I have now disabled it, and it's still around.

Reply
0 Kudos
Shylidi
Contributor
Contributor

Here's the client plugin page.

Reply
0 Kudos
bryanvaneeden
Hot Shot
Hot Shot

What is the error message in the Client Plugin page, and what did your search through the log files yield?

Visit my blog at https://vcloudvision.com!
Reply
0 Kudos
kluusi
Contributor
Contributor

 

Hi,

Same Issue here after VCSA Update to Version:7.0.1.00200 Build-Nummer 17327517.

Unregister via SSH-Shell does not work...

 

See the list of the duplicate entries:

 

Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M -Dcom.sun.org.apache.xml.internal.security.ignoreLineBreaks=true -Dorg.apache.xml.security.ignoreLineBreaks=true
Service Product: com.vmware.h4
Service Type: vsphere.client
Service ID: b584a78a-8cb0-4b43-bb59-2dadcf767ff9
Site ID: default-site
Version: 0.4.0.0
Endpoints:
Type: com.vmware.cis.vsphereclient.plugin
Protocol: http
URL: https://VCENTER-SRV-NAME:443/ui/plugins/h4va.zip

-------------------------------------------------------
Service Product: com.vmware.h4
Service Type: vsphere.client
Service ID: e034cd0a-fa80-4294-9b3a-1be3ef8cbdb9
Site ID: default-site
Version: 0.4.1.0
Endpoints:
Type: com.vmware.cis.vsphereclient.plugin
Protocol: http
URL: https://VCENTER-SRV-NAME:443/ui/plugin-resources/h4va.zip


BR Klaus

 

Reply
0 Kudos
bryanvaneeden
Hot Shot
Hot Shot

And what do the vSphere Client/UI log say on this?

Visit my blog at https://vcloudvision.com!
Reply
0 Kudos
ChrisJMo
Contributor
Contributor

Hi!

I have the same problem.

Seems it has something to do with Upgrade to 7.0.1.00200

Reply
0 Kudos
Shylidi
Contributor
Contributor

I can confirm from my end the upgrade was involved, I ended up reinstalling my vCenter server, and now I'm in the clear.

Reply
0 Kudos
2978696269
Contributor
Contributor

Hello,

unregistering obsolete plugin with lstool.py script worked fine for me on VCSA 7.0.1.00200 build 17327517.

-------------------------------------------------------
Service Product: com.vmware.h4
Service Type: vsphere.client
Service ID: 643a9443-902e-433f-b857-4603e14d9fc8
Site ID: default-site
Node ID: 042705b7-e1eb-49d1-aa14-131c2600fd2f
Owner ID: vsphere-webclient-bc0fb587-9d41-48c1-8b37-9f0f852c34b5@vsphere.local
Version: 0.3.5.0
Endpoints:
Type: com.vmware.cis.vsphereclient.plugin
Protocol: http
URL: https://vcsa:443/ui/plugins/h4va.zip
SSL trust: ***
Attributes:
com.vmware.cis.cm.HostId: bc0fb587-9d41-48c1-8b37-9f0f852c34b5
-------------------------------------------------------
Service Product: com.vmware.h4
Service Type: vsphere.client
Service ID: cb6deca2-56af-457f-8f6b-3ce0232eca7c
Site ID: default-site
Node ID: 042705b7-e1eb-49d1-aa14-131c2600fd2f
Owner ID: vsphere-webclient-bc0fb587-9d41-48c1-8b37-9f0f852c34b5@vsphere.local
Version: 0.4.1.0
Endpoints:
Type: com.vmware.cis.vsphereclient.plugin
Protocol: http
URL: https://vcsa:443/ui/plugin-resources/h4va.zip
SSL trust: ***
Attributes:
com.vmware.cis.cm.HostId: bc0fb587-9d41-48c1-8b37-9f0f852c34b5
-------------------------------------------------------

/usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url http://localhost:7090/lookupservice/sdk --user administrator@vsphere.local --password *** --id 643a9443-902e-433f-b857-4603e14d9fc8 --no-check-cert

In the end only version 0.4.1.0 left registered.

 

bryanvaneeden
Hot Shot
Hot Shot

This would be the last rigorous way that I would advise, but yes that would do the trick since you are essentially removing it from the database. 

Visit my blog at https://vcloudvision.com!
Reply
0 Kudos
Detavern
Contributor
Contributor

Hi,

Same Issue here after VCSA update to version: 7.0.1.00200 Build-Number 17327517 from 7.0.1.00100.

There should be sth broken with update 7.0.1.00200.

Comfirmed unregister that duplicated plugin works for me.

Reply
0 Kudos
discofris
Contributor
Contributor

  1. /usr/lib/vmware-lookupsvc/tools/lstool.py list --ep-type com.vmware.cis.vsphereclient.plugin --url  http://localhost:7090/lookupservice/sdk

  2. Look for the Service ID of Version 0.4.0.0 of the plugin

  3. /usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url http://localhost:7090/lookupservice/sdk --user administrator@vsphere.local --password ****** --id e58ecbfe-514c-4940-95f7-775bc0348ac0 --no-check-cert

  4. vmon-cli -r vsphere-ui

Succesfully executed on a VCSA 7.0.1.00200 Build 17327517

Ajay1988
Expert
Expert

Please follow this -https://virtual-power.in/f/plugin-under-client-plugin-in-html-shows-in-failed-status

 

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ
Reply
0 Kudos