vmware-sps, vmware-content-library, vmware-updatemgr services failing to start
search cancel

vmware-sps, vmware-content-library, vmware-updatemgr services failing to start

book

Article ID: 322340

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Inventory information is missing from the vCenter HTML5 client

The following can be found in the vCenter logs

/var/log/vmware/vmware-sps/sps.log

YYY-MM-DDTHH:MM:SS.###Z [main] ERROR opId=sps-Main-######-### com.vmware.vim.storage.common.serviceclient.ls.impl.ExternalServiceRegistryImpl - LS returned null or empty result, for filter={product = com.vmware.cis, type = vcenterserver, nodeId = ########-###-####-####-############}
YYY-MM-DDTHH:MM:SS.###Z [main] ERROR opId=sps-Main-######-### com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientLifeCycle - Error while getting VPXD principal id
com.vmware.vim.storage.common.serviceclient.ls.LsException: Could not find VC info
        at com.vmware.vim.storage.common.serviceclient.ls.LsException.from(LsException.java:35) ~[storage-commons-1.0.jar:?]
        at com.vmware.vim.storage.common.serviceclient.ls.impl.ExternalServiceRegistryImpl.findVc(ExternalServiceRegistryImpl.java:214) ~[storage-commons-1.0.jar:?]
        at com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientLifeCycle.getPrincipalId(VpxdClientLifeCycle.java:132) ~[storage-commons-1.0.jar:?]
        at com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientManagerImpl.getPrincipalId(VpxdClientManagerImpl.java:308) ~[storage-commons-1.0.jar:?]
        at com.vmware.vim.storage.common.security.CommonSessionManager.initVpxdPrincipalId(CommonSessionManager.java:102) ~[storage-commons-1.0.jar:?]

/var/log/vmware/content-library/cls.log

YYY-MM-DDTHH:MM:SS.###Z | WARN     | null             | main                      | GenericXmlApplicationContext   | Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'updateSessionService': Unsatisfied dependency expressed through field 'storageService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'storageService': Unsatisfied dependency expressed through field 'typeAdapterService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'typeAdapterService': Unsatisfied dependency expressed through field 'httpClientBuilderFactory'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'httpClientBuilderFactory': Unsatisfied dependency expressed through field 'applianceProxySettings'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'applianceProxySettings' defined in class path resource [cls-unified/spring/cl-common-services-context.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.vcde.common.services.proxy.ApplianceProxySettings]: Constructor threw exception; nested exception is com.vmware.vcde.common.services.exceptions.ServiceNotFoundException: com.vmware.cis:vcenterserver

Environment

VMware vCenter Server

 

Cause

This issue is caused by a missing service registration that fetched during services startup, hence we see error as Could not find VC info

Resolution

  • Before executing any changes or repairs, take offline snapshots and backups of all vCenters in the SSO domain or in Enhanced Linked Mode.
  • Enter a shell session with the vCenter appliance through SSH
  • Download the ldsoctor tool from Using the 'lsdoctor' Tool
  • Upload lsdoctor.zip file using WINSCP or any similar tool to the vCenter appliance under the "/root/" directory
    • When running the tool, be sure you are currently in the “lsdoctor-master” directory.
  • Run “python lsdoctor.py -r”
  • Provide the password for your SSO administrator account when prompted
  • The following menu will be presented:

  
  • Recreate the specific service registration(s) of vCenter Server using option 3, or re-create all service registrations using option 2
  • Restart services using the following command:
      service-control --stop --all && service-control --start –all
  • Validate that all services come online and the inventory information is properly populating within the vCenter appliance

Additional Information

Powered by Wolken Software