Found a detailed KB article from VMware on this but they reference this happens when you have a proxy in place, which we don't so seems this problem can potentially affect more environments.
Solution for vCSA:
service vsphere-client stop
rm -rf /usr/lib/vmware-vsphere-client/server/work/*
rm /usr/lib/vmware-virgo/server/pickup/*
/usr/lib/vmware-vsphere-client/plugin-packages/vsphere-client/plugins/
:- telemetry-service-6.0.0.jar
- telemetry-ui-war-6.0.0.war
- phonehome-collector-ui-war-6.0.0.war
- cis-data-service-cmc-6.0.0.jar
/usr/lib/vmware-vsphere-client/plugin-packages/vsphere-client/plugins/
:- telemetry-service-6.0.0.jar
- telemetry-ui-war-6.0.0.war
- phonehome-collector-ui-war-6.0.0.war
- cis-data-service-cmc-6.0.0.jar
service vsphere-client start
Links:
No comments:
Post a Comment