«

»

vCenter Server Services Fails To Start After Upgrade To 6.7 U2c

A while back I did a VMware vCenter Server upgrade, version 6.7 to version 6.7 U2c. The upgrade completed successfully but some services including e.g. vmware-vpxd didn’t start.

Checking the vCenter Server Appliance Management Interface (VAMI) I could see that quite a few services with Startup Type Automatic was not running and service “VMware vCenter-Services” was in state Starting.

Verified the same thing by logging into the vCenter Server Appliance (VCSA) using SSH and running the command:

service-control –status

The result I got was:

Stopped:
pschealth vmcam vmware-content-library vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-rbd-watchdog vmware-rhttpproxy vmware-sca vmware-sps vmware-topologysvc vmware-updatemgr vmware-vapi-endpoint vmware-vcha vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsan-dps

Running:
applmgmt lwsmd vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-certificatemanagement vmware-cis-license vmware-cm vmware-eam vmware-pod vmware-postgres-archiver vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-vmon vmware-vpostgres vsphere-client vsphere-ui

Decided to try a manual stop and start procedure since I know this has solved similar problems before. Via a VCSA SSH session I did:

  • service-control –stop
    • Output according to:
      Operation not cancellable. Please wait for it to finish…
      Performing stop operation on service vmware-pod…
      Successfully stopped service vmware-pod
      Performing stop operation on profile: ALL…
      Successfully stopped service vmware-vmon
      Successfully stopped profile: ALL.
  • service-control –start
    • Output according to:
      Operation not cancellable. Please wait for it to finish…
      Performing start operation on profile: ALL…
      Successfully started service vmware-vmon
      Successfully started profile: ALL.
      Performing start operation on service vmware-pod…
      Successfully started service vmware-pod

Checking the status again using command “service-control –status” gave the following good output:

Running:
applmgmt lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-certificatemanagement vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-pod vmware-postgres-archiver vmware-rbd-watchdog vmware-rhttpproxy vmware-sca vmware-sps vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-topologysvc vmware-updatemgr vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui

Stopped:
vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-vcha vsan-dps

Going back to the VAMI and checking the services it all looks good.

— Case closed/problem solved —

5 pings

Comments have been disabled.