Virgo logs are where plugin log information is stored for the vCenter.
Virgo logs for the HTML plugin are located at /var/log/vmware/vsphere-ui/logs live on the vCenter and at the same path in the support bundle from Capturing VMware Support Bundles.
The most recent log file is vsphere_client_virgo.log. Log files are rolled and compressed periodically and will be renamed to vsphere_client_virgo_x.log.zip
.
When searching the virgo logs for issues related to the Pure Plugin, there can be a lot of information that isn't related to the Pure plugin. Using less, searching for com.purestorage.purestoragehtml is helpful because this will pull up information related to the Pure vCenter plugin.
Starting in vSphere Plugin version 5.2.0, logs from the plugin are phoned home by default but users are able to disable phone home. They are labeled external_rest.log and, similar to the REST logs, will only phone home to the FlashArray if there were any calls made.
Removing Stale vSphere Plugin Files from vCenter
If a customer states that none of the above methods completely remove the plugin (i.e. All of the uninstall methods report "successful" but the plugin is still shown in vCenter) then you can walk them through the following steps to clean up any residual files:
Step 1. SSH to the vCenter Server with an account that has administrative privileges.
Step 2. Type shell to enter BASH.
Step 3. Run the following commands:
root@vcsa[~]# cd /
root@vcsa[/]# find -name "*purestorage*"
It is important to note that the customer might have BOTH the Flash and HTML plugin installed on their vCenter Server. If they have both installed please STOP HERE and open a JIRA with the output from "Step 3" and guidance can be provided on how to move forward. This will ensure a proper action plan is provided so that necessary files for the other plugin are not erroneously removed.
Step 4. If there are still residual files then they can be cleaned up as follows:
root@vcsa[/]# find -name "*purestorage*" -exec rm -r {} \;
5. Once the files have all been cleaned up log out of the vCenter GUI (if logged in).
6. Once you are logged out of the vCenter GUI restart the vSphere Web Client service for the changes to take affect:
root@vcsa[/]# service-control --stop vsphere-ui
root@vcsa[/]# service-control --start vsphere-ui 7. Once the vSphere Web Client service has been restarted log back into the vCenter GUI and confirm the plugin is no longer listed.
If the plugin is still reported in vCenter after taking the action listed above the only step left is to reboot the vCenter Server. This doesn't happen often and should be the exception not the rule.