Error: vCenter services fail to start after power outage
search cancel

Error: vCenter services fail to start after power outage

book

Article ID: 440464

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

After an Data center power outage or power off of the vCenter VM, the vCenter server appliance (VCSA) services fail to start. Many remain in Start Pending or Stopped state.

While connected to SSH or a remote console of the affected vCenter VM, the following symptoms are observed:

  • One of the first messages that appears on screen notes a failure to connect to applmgmt service:
    failed to connect to service. Use service-control command to manage applmgmt service.

     

  • Applmgmt service is in StartPending or Stopped state when viewing the status of all services:
    service-control --status --all

Note: Multiple Services will be in stopped state, as there are many dependencies with the services. In some cases Certificate can be a issue due to which multiple services would fail.

Environment

vCenter 8.x

Cause

Services often fail to start after a power outage because they cannot reach the Domain Controller or DNS servers. Expired security certificates cause similar issues.

Resolution

To resolve the issue, try any of the 2 below steps.

Step 1

  1. Connect to the vCenter server Putty session.

  2. Run the command below to start all the services.
    service-control --start --all

Step 2

If certs are expired perform the below steps to resolve the issue.

Use vCert to renew the Machine SSL certificate and ensure that the vCenter's IP address is included in the Subject Alternative Name (SAN).

  1. Start the vCert tool in the affected vCenter:
  2. Confirm that the Machine SSL certificate does not contain the vCenter's IP address in SAN:
    1. In the main menu of vCert, go to option 2. View certificate Info

    2. For the View vCenter Certificates menu, go to option 1. Machine SSL Certificate

    3. Verify that the certificate is missing the vCenter's IP address under Subject Alternative Names (SAN)

  3. Return to the main menu of vCert and enter 3. Manage Certificates

  4. For the Manage vCenter Certificates menu, enter option 1. Machine SSL Certificate

  5. Choose to replace the Machine SSL certificate according to your intended certificate signer.
    1. When prompted with "Enter an IP address (optional)", input the vCenter's IP address.

  6. To be thorough, under the Manage vCenter Certificates menu, choose option 2. Solution User certificates and replace the Solution User certificates accordingly

  7. Once the above steps complete, restart the affected vCenter's services:
    service-control --stop --all && service-control --start --all
  8. Confirm that vCenter services are running as expected:
    service-control --status --all

Additional Information

If DNS servers are not online then follow the Step to add the host file entry to resolve the DNS issue.

  • Add fqdn resolution in /etc/hosts temporarily to have vCenter Manageable to start DNS servers

Related KB: "Error: Failed to start services in profile ALL" when updating Machine SSL Certificate by certificate-manager when vCenter PNID is IP Address