VMware Update Manager service stops immediately after starting or crashes after restoring vCenter or Platform Service Controller(PSC) from snapshot
Article ID: 316495
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Symptoms:
[2019-08-27 15:37:51,287 ERROR] Unable to update VUM service info
Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment.
- Update Manager service stops immediately after starting or crashes after restoring vCenter or PSC from snapshot.
- Update Manager service fails to start after restoring the VC or PSC from backup.
- Update manager service fails to start post failed converge in VCSA 6.7.
- In refreshCerts-utility.log file you will see entries similar to the below
[2019-08-27 15:37:51,287 ERROR] Unable to update VUM service info
Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment.
Environment
VMware vCenter Server Appliance 6.7.x
Cause
This issue is caused either by
- Missing update manager service information either by restoring the PSC or VC from a invalid backup.
OR
- VUM service is deleted.
Resolution
To resolve this issue, follow the steps below, do not skip any step.
1. Export the VUM service to a spec file from a working VCSA with same version or use the attachment Sample spec file_VUM in this article.
2. To export the VUM service to a spec file, use the following command:
/usr/lib/vmidentity/tools/scripts/lstool.py get --url "https://localhost/lookupservice/sdk" --id "84721bf9-5568-4905-9228-d2b6583d4797" --no-check-cert --as-spec > /tmp/spec.txt
3. The serviceID (GUID) can be obtained using the below command:
grep -i integrity /etc/vmware/rereg/*
/etc/vmware/rereg/84721bf9-5568-4905-9228-d2b6583d4797_spec.serviceType.type = vcIntegrity
Note that you will only fill the spec file with the GUID, shown in bold above. Be sure to use the value from your environment, the above is only an example.
Note: You may see two different specs as result of this command. One of the them the serviceType.product is for vcIntegrity and the other one is for com.vmware.vum. We should get the one where the serviceType.product contains vcIntegrity.
4. Fill the spec file with the serviceID, serviceVersion, ownerId, nodeId, ssltrust, and Endpoint URL values that correspond to your environment.
5. The serviceVersion value can be found by running the command below:
cat /usr/lib/vmware-updatemgr/firstboot/updatemgr-h5.properties
6. The ownerID can be found from the lstool.py output. For information on how to run this command, see KB: https://kb.vmware.com/s/article/2043509
The ownerID should be in a format like:
vpxd-extension-<GUID>@<SSO_DOMAIN>
Be careful to choose the correct owner in environments with multiple vCenter Server nodes, as there will be multiple values. The GUID should match the machine ID, which you can obtain with the following command:
/usr/lib/vmware-vmafd/bin/vmafd-cli get-machine-id --server-name localhost
7. The nodeID can be obtained from by running the command:
/usr/lib/vmware-vmafd/bin/vmafd-cli get-ldu --server-name localhost
8. The ssltrust value will be the machine SSL certificate, which you can find in the lstool.py output as well.
9. Register the VUM using the spec file by entering the below command:
/usr/lib/vmidentity/tools/scripts/lstool.py register --spec /tmp/spec.txt --url https://localhost/lookupservice/sdk --user [email protected] --password "password" --id "84721bf9-5568-4905-9228-d2b6583d4797" --no-check-cert
10. Register VUM with the vCenter using the command below:
/usr/lib/vmware-updatemgr/bin/updatemgr-utility.py register-vc
11. Start the update manager service:
service-control --start vmware-updatemgr
/usr/lib/vmidentity/tools/scripts/lstool.py get --url "https://localhost/lookupservice/sdk" --id "84721bf9-5568-4905-9228-d2b6583d4797" --no-check-cert --as-spec > /tmp/spec.txt
3. The serviceID (GUID) can be obtained using the below command:
grep -i integrity /etc/vmware/rereg/*
/etc/vmware/rereg/84721bf9-5568-4905-9228-d2b6583d4797_spec.serviceType.type = vcIntegrity
Note that you will only fill the spec file with the GUID, shown in bold above. Be sure to use the value from your environment, the above is only an example.
Note: You may see two different specs as result of this command. One of the them the serviceType.product is for vcIntegrity and the other one is for com.vmware.vum. We should get the one where the serviceType.product contains vcIntegrity.
4. Fill the spec file with the serviceID, serviceVersion, ownerId, nodeId, ssltrust, and Endpoint URL values that correspond to your environment.
5. The serviceVersion value can be found by running the command below:
cat /usr/lib/vmware-updatemgr/firstboot/updatemgr-h5.properties
6. The ownerID can be found from the lstool.py output. For information on how to run this command, see KB: https://kb.vmware.com/s/article/2043509
The ownerID should be in a format like:
vpxd-extension-<GUID>@<SSO_DOMAIN>
Be careful to choose the correct owner in environments with multiple vCenter Server nodes, as there will be multiple values. The GUID should match the machine ID, which you can obtain with the following command:
/usr/lib/vmware-vmafd/bin/vmafd-cli get-machine-id --server-name localhost
7. The nodeID can be obtained from by running the command:
/usr/lib/vmware-vmafd/bin/vmafd-cli get-ldu --server-name localhost
8. The ssltrust value will be the machine SSL certificate, which you can find in the lstool.py output as well.
9. Register the VUM using the spec file by entering the below command:
/usr/lib/vmidentity/tools/scripts/lstool.py register --spec /tmp/spec.txt --url https://localhost/lookupservice/sdk --user [email protected] --password "password" --id "84721bf9-5568-4905-9228-d2b6583d4797" --no-check-cert
10. Register VUM with the vCenter using the command below:
/usr/lib/vmware-updatemgr/bin/updatemgr-utility.py register-vc
11. Start the update manager service:
service-control --start vmware-updatemgr
Attachments
Feedback
Yes
No
Powered by
