How to clean the web client cache and remove unwanted plugins for vSphere Replication, Site Recovery Manager and Site Recovery Plugin 8.x versions
search cancel

How to clean the web client cache and remove unwanted plugins for vSphere Replication, Site Recovery Manager and Site Recovery Plugin 8.x versions

book

Article ID: 312655

calendar_today

Updated On:

Products

VMware Live Recovery VMware vCenter Server VMware vSphere ESXi

Issue/Introduction


How to clean the Web Client Cache and remove unwanted plugins.

Symptoms:

Missing Plugins for vSphere Replication, Site Recovery Manager and Site Recovery Plugin Ui (8.x)

Environment

VMware vCenter Site Recovery Manager 8.x
VMware vCenter Server 6.5.x
VMware vCenter Site Recovery Manager 6.5.x
VMware vSphere Replication 8.x
VMware vSphere Replication 6.5.x

Cause


Missing plugins in web/HTML client. New Plugin deployed does load in the vSphere Web Client.

You performed a rollback to previous version OR you have incorrect installations and upgrades.

You will see error messages in the vSphere web Client Logs
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.monitoring.doc/GUID-7E10C58F-16EA-44AB-8AA0-8D4A66399879.html

vsphere_client_virgo.log - Contains all the communication between underlying Flex endpoint connections, internal tasks, and events. This is the mainvSphere Web Clientlog fil

Appliance 

/var/log/vmware/vsphere-client/logs
NOTE: Replace vsphere-client with vsphere-ui for HTML 

Windows

C:\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs

Resolution


Verify if you have unwanted plugins for vCenter Appliance.

vSphere replication(vcHms). Site Recovery Manager (vcDr). Site Recovery Plugin 8.x (vrUi) 

1. Take snapshot to avoid human error on input of commands.

 If the vCenters are in a Linked Mode Deployment.  Perform the below actions on all vCenters at the same time, One by One.

Please take snapshots of SRM, VR & vCenter/PSC appliances as necessary before performing any actions mentioned in the resolution section. Refer to VMware vCenter in Enhanced Linked Mode pre-changes snapshot (online or offline) best practice (85662)

2.Check for plugin packages. Open an SSH connection to vCenter and navigate to the below folders.

ls /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
ls /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/

ls /etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin
ls /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin

SRM = vcDr, vSphere Replication = vcHms; vrms, Site recovery plugin = vRui

Note the files inside these packages

Example vr.6.5.1.xxx.war and .jar files will still be referenced in pickup folder step 8.

3. If incorrect build numbers for plugins are present. 

Stop the Web Client and vSphere Ui service

service-control --stop vsphere-client; service-control --stop vsphere-ui

4.Clear the user cache:

cd /storage/vsphere-client/SerenityDB/serenity/

This directory is to be completely emptied. (you can use rm -rf * when in the directory)

5. Clean tomcat cache

cd /usr/lib/vmware-vsphere-client/server/work/
 
This directory is to be completely emptied.

6. Clear the unwanted plugin packages 

cd /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
cd /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/

Only the relevant older vcDr and vcHms plugin package are to be removed. The solution for SRM and vSphere Replication needs to be re-registered afterwards. 

Example if Running Site recovery 6.5.1.3 or 8.x
com.vmware.vcHms6.5.1, 
com.vmware.vcDr.5.8.1

Site Recovery 8.x plugin packages
cd /etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin
cd /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin

Only the relevant older vRui plugin package is to be removed.

Example if running Site recovery 8.2
rm -r com.vmware.vrUi-8.1.0
 
7. Clear the CmCatalog of plugin zip files.

cd /etc/vmware/vsphere-client/cmCatalog
cd /etc/vmware/vsphere-ui/cmCatalog

Example
rm com.vmware.cis.com.vmware.vcDr.zip
rm com.vmware.cis.com.vmware.vcHms.zip

8. Clear the Pickup folder.

cd /usr/lib/vmware-vsphere-client/server/pickup

Example
rm vr.6.5.1xxxxx.

Only the older stale relevant vcDr and vcHms plugins are to be removed.

9. Start the Web Client and vSphere Ui service

service-control --start vsphere-client ; service-control --start vsphere-ui

10. Confirm Web Client functionality and consolidate the snapshots.

================================================

Web client cache Windows locations 6.5 for rollback of Site Recovery 8.x
------------------------------------------------------------------------------------------------
1. Take snapshot to avoid human error on input of commands.

 Stop Web Client and Ui service

cd C:\Program Files\VMware\vCenter Server\bin
service-control --stop vspherewebclientsvc
service-control --stop vsphere-ui; 
    
2. C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\      remove any vcDr or vcHms packages that are not compatible
    C:\ProgramData\VMware\vCenterServer\cfg\vsphere-ui\vc-packages\vsphere-client-serenity\

   Note the plugins .war and .jar files for the next step 3.

3. C:\ProgramData\VMware\vCenterServer\runtime\vsphere-client\server\pickup\                  remove vcDr and vcHms .war +.jar files. They will relate to the files referenced in the plugin package in Step 3.

4. C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\cmCatalog\                                 empty folder
    C:\ProgramData\VMware\vCenterServer\cfg\vsphere-ui\cmCatalog\                                       empty folder

5. C:\ProgramData\VMware\vCenterServer\runtime\vsphere-client\server\work                         empty folder
    C:\ProgramData\VMware\vCenterServer\runtime\vsphere-ui\server\work                               empty folder 

6. C:\ProgramData\VMware\vCenterServer\runtime\vsphere-ui\server\pickup                            empty folder
    
7. C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity           empty folder 

8. Site Recovery 8.x Ui folders 

C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\cm-service-packages\com.vmware.cis.vsphereclient.plugin\
C:\ProgramData\VMware\vCenterServer\cfg\vsphere-ui\cm-service-packages\com.vmware.cis.vsphereclient.plugin\ 

9. Start Web Client vSphere Ui

service-control --start vspherewebclientsvc
service-control --start vsphere-ui; 

10. Confirm Web Client functionality and consolidate the snapshots.

Workaround:
None

Additional Information

VMware Skyline Health Diagnostics for vSphere - FAQ

Impact/Risks:
Restarting the web client and UI service will kick users out. Also, restarting all vCenter services when backups are running will stall all running backup jobs.

Powered by Wolken Software