Content-library service on vCenter Server fails to start - Failed to find the endpoint type: com.vmware.vapi.endpoint

Products

• VMware vCenter Server

Issue/Introduction

After experiencing ELM replication issues, the content-library service fails to start.

The log file /var/log/vmware/content-library/cls.log contains a warning similar to the following:

2025-12-09T22:23:23.919Z | WARN | null | main | LookupManagerImpl | Failed to find the endpoint type: com.vmware.vapi.endpoint, protocol: vapi.json.https, local protocol: vapi.json.http, local: false from
 service (lookup.Info) {
   dynamicType = null,
   dynamicProperty = null,
   serviceVersion = 1.0,
   vendorNameResourceKey = ,
   vendorNameDefault = ,
   vendorProductInfoResourceKey = ,
   vendorProductInfoDefault = ,
   serviceEndpoints = (lookup.Endpoint) [

Environment

vCenter Server Appliance 8.x

Cause

When dealing with broken ELM replication issues, its possible that one more endpoint registrations for internal and external service communication to become invalid or missing.  In the case of the content-library service and error "Failed to find the endpoint type: com.vmware.vapi.endpoint, protocol: vapi.json.https, local protocol: vapi.json.http", this points to the "cs.vapi" service registration of endpoints.

Resolution

CAUTION: Only proceed if you have resolved all ELM replication issues in the ELM group.  If this hasn't been done, please do so before running any of the following steps.

To resolve the issues with starting the content-library service, use lsdoctor to rebuild the cs.vapi service registration.

lsdoctor can be obtained here.

NOTE:  As always, take safe offline snapshots as a pre-requisite to running lsdoctor.

Once lsdoctor has been deployed on the vCenter, run:

1. Run lsdoctor with the rebuild option:

   1. python lsdoctor.py -r

2. When prompted, select Option 3 (Replace individual service.)
3. You will be presented with a list of services.  Select the number that corresponds to "cs.vapi".
4. After exiting lsdoctor, restart all services: 

   1.  service-control --stop --all && service-control --start --all