Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Update Manager service stops immediately after starting or crashes after restoring vCenter or PSC (74617)

Last Updated: 11/9/2023Categories: TroubleshootingTotal Views: 17299Language:
SpanishEnglish

10 like this article

Subscribe to get an email
newsletter with new updates

10 people found this helpful Please provide article feedback:

Symptoms

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,286 ERROR] Unable to retrieve VUM serviceInfo, count=0, ldu-guid=bf108140-52ce-11e7-89c9-005056a44097, property_file=/usr/lib/vmware-updatemgr/firstboot/updatemgr-h5.properties
[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.

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-masked] --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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
SpanishEnglish

Attachments

Sample spec file_VUM

Additional Resources

KB
•
"Unable to find VUM extension registered with VC" error while registering Update Manager with vCenter Server Appliance (2151622)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant