Problem:
I was trying to publish a content library externally, so I could access it from a different cluster. However, I couldn't find it. This situation makes me doubt for a while if I really had created this content library, but, I was sure I did. So dude, where’s my content library?
![19.p36 Image01 Missing Content Library](https://i0.wp.com/mulcas.com/mulcas_uploads/2019/03/19.p36_Image01.png?resize=300%2C90&ssl=1)
I had to reboot the ESXi (6.7), and the VCSA sited on it for maintenance purpose, and after this, the issue was presented. Investigating a bit more, finally, notice that the Content Library Service never started, it was Stopped.
![19.p36 Image02 Missing Content Library service](https://i0.wp.com/mulcas.com/mulcas_uploads/2019/03/19.p36_Image02.png?resize=300%2C70&ssl=1)
Solution:
Make sure that the content Library Service is started.
- Access the VCSA via SSH.
- Run the following command to check the Content Library services status.
service-control --status vmware-content-library
- If the service is Stopped, run the following commando to start it.
service-control --start vmware-content-library
- The Content Library Service will start.
![19.p36 Image03 Missing Content Library service](https://i0.wp.com/mulcas.com/mulcas_uploads/2019/03/19.p36_Image03.png?resize=300%2C105&ssl=1)
After following the steps above, the Content Library should be visible from the vSphere Client.
![19.p36 Image04 Content Library](https://i0.wp.com/mulcas.com/mulcas_uploads/2019/03/19.p36_Image04.png?resize=300%2C97&ssl=1)
Other solutions:
VMware can be funny sometimes… if for some reasons you are unable to start the Content Library service, try out this workaround from VMware KB.