Error 500 An error occurred while fetching identity providers. Try again"Service-control failed. Error: Failed to start services in profile ALL. RC=1, stderr=Failed to start hvc, vpxd, vapi-endpoint, vpxd-svcs services. Error: Operation timed out"#root@vcsa: service-control --start --allOperation not cancellable. Please wait for it to finish...Performing start operation on service lwsmd...Successfully started service lwsmdPerforming start operation on service vmafdd...Successfully started service vmafddPerforming start operation on service vmdird...Successfully started service vmdirdPerforming start operation on service vmcad...Successfully started service vmcadPerforming start operation on profile: ALL...Successfully started service vmware-vmonService-control failed. Error: Failed to start services in profile ALL. RC=1, stderr=Failed to start hvc, vpxd, vapi-endpoint, vpxd-svcs services. Error: Operation timed out
YYYY-MM-DDTHH:MM:SS Wa(03) host-xxxx <vpxd-svcs> Service pre-start command's stderr: Traceback (most recent call last):YYYY-MM-DDTHH:MM:SS Wa(03)+ host-xxxx File "/usr/lib/vmware-vpxd-svcs/scripts/linux/pre-start/tagging_grpc_registration.py", line 116, in update_endpointsYYYY-MM-DDTHH:MM:SS Wa(03)+ host-xxxx ls_obj.reregister_service(service_info.serviceId, mutable_spec)YYYY-MM-DDTHH:MM:SS Wa(03)+ host-xxxx File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 349, in add_securityctx_to_requests
YYYY-MM-DDTHH:MM:SS Wa(03)+ host-xxxx pyVim.sso.SoapException: SoapException:YYYY-MM-DDTHH:MM:SS Wa(03)+ host-xxxx faultcode: ns0:FailedAuthenticationYYYY-MM-DDTHH:MM:SS Wa(03)+ host-xxxx faultstring: Invalid credentialsYYYY-MM-DDTHH:MM:SS Wa(03)+ host-xxxx faultxml: <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode xmlns:ns0="http://docs.oasis-open.org/ws-sx/ws-trust/200512">ns0:FailedAuthentication</faultcode><faultstring>Invalid credentials</faultstring></S:Fault></S:Body></S:Envelope>
VMware vCenter Server 8.0.x
VMware vCenter Server 7.0.x
This issue is caused due to the certificates being expired on the vCenter server
Note: Ensure to take a powered off snapshot on VCSA prior to proceeding with the steps below. In case of Enhanced Linked Mode (ELM), ensure to take a powered off snapshot on all the nodes in ELM.
Use the new improved certificate management tool vCert - Scripted vCenter Expired Certificate Replacement for all certificate management/replacement workflow. The KB has detailed steps to replace the expired certificates.
Determining expired SSL certificates in vCenter Server: https://knowledge.broadcom.com/external/article/343041/determining-expired-ssl-certificates-in.html