Another day another case… This time, I was surprised to see an empty list when provisioning a new virtual machine from a Content Library.
I went to check the Content Library status and found all templates were shown as ‘Unknown’ in there.
Funny enough, this behaviour was happening only with the local Content Library. A subscribed one didn’t have any issues at all, and the synchronisation between those two was still working.
More interestingly, the objects of other types were not affected at all.
There is not enough information about how to troubleshoot the Content Library in vSphere 6.0. Some of the diagnostic files can be found in the /var/log/vmware/vdcs directory on vCenter Server Appliance (VCSA). Unfortunately, they are not that informative.
So I opened the case with VMware GSS (SR # 17504701707) and the response was that “this issue is occurring as there is a corrupted or stale PID for the content library service which has not been cleared from the previous running state.”
VMware is working on this to be resolved, but no ETA at the moment.
A workaround provided by VMware:
- Connect to the vCenter Server Appliance using SSH and root credentials.
- Navigate to /var/log/vmware/vdcs.
- Create a new folder to move the PID file to.
- Move the vmware-vdcs.pid file to the folder created in step 3.
- Reboot the vCenter Server Appliance (In case of external PSC, reboot the PSC first and then the vCenter).
I personally found that restarting VCSA resolves this issue. However, it reappears after some time.