Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
vCenter is down and will not start upon attempting.vCenter services status: root@vcenter [ /tmp ]# service-control --status Running: applmgmt lookupsvc lwsmd observability-vapi pschealth vlcm vmafdd vmcad vmdird vmonapi vmware-analytics vmware-certificateauthority vmware-certificatemanagement vmware-cis-license vmware-eam vmware-envoy vmware-hvc vmware-infraprofile vmware-perfcharts vmware-postgres-archiver vmware-rhttpproxy vmware-sca vmware-statsmonitor vmware-stsd vmware-topologysvc vmware-trustmanagement vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd-svcs vmware-vsm vsphere-ui vtsdb Stopped: observability vmcam vmware-content-library vmware-imagebuilder vmware-netdumper vmware-pod vmware-rbd-watchdog vmware-sps vmware-updatemgr vmware-vcha vmware-vdtc vmware-vpxd vmware-vsan-health vstats wcp STS and certificates are valid. Check STS cert on VCSA/Windows: https://kb.vmware.com/s/article/79248 Check & Replace other certs on vCenter: https://kb.vmware.com/s/article/68171 sometimes vpxd.log will not update an error or logs are missing.
VCLS VMs were deleted or misconfigured and then vCenter was rebooted.
VCLS VMs were deleted and or previously misconfigured and then vCenter was rebootedAs a result for previous action, vpxd.cfg file was left with wrong data preventing vpxd service from starting. you may visit VCLS KB https://kb.vmware.com/s/article/80472 for more information on VCLS configuration.
vCenter won't start if it got rebooted.
Do not skip any steps please do follow all the below-provided steps. Connect to VCSA using SSH session with rootTake a backup from file /etc/vmware-vpx/vpxd.cfgConfirm vpxd is not running / Stop vpxd using : service-control --stop vpxdEdit file vpxd.cfg vi vpxd.cfgRemove the part that contains vcls section, looks like below: <vcls> <clusters> <domain-c22> <enabled>False</enabled> </domain-c22> <domain-c22:f696e05a-6cf8-4d02-af1c-10e81f90ec81> <enabled>False</enabled> </domain-c22:f696e05a-6cf8-4d02-af1c-10e81f90ec81> <domain-c86> <enabled>false</enabled> </domain-c86> <f696e05a-6cf8-4d02-af1c-10e81f90ec81> <enabled>False</enabled> </f696e05a-6cf8-4d02-af1c-10e81f90ec81> </clusters> </vcls> Then save the file and exitStart vpxd using : service-control --start vpxdvCenter should be accessible now
About VCLS: https://kb.vmware.com/s/article/80472 https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-96BD6016-4BE7-4B1C-8269-568D1555B08C.html#:~:text=In%20vSphere%207.0%20U2%2C%20vSphere,that%20run%20in%20the%20clusters Check STS cert on VCSA/Windows: https://kb.vmware.com/s/article/79248Check & Replace other certs on vCenter: https://kb.vmware.com/s/article/68171