Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Tag associations are not removed from vCenter Server database when associated objects are removed or deleted (58840)

Last Updated: 3/11/2024Categories: How toTotal Views: 6650Language:
English

12 like this article

Subscribe to get an email
newsletter with new updates

12 people found this helpful Please provide article feedback:

Symptoms

Virtual Machine tag associations are not deleted from the vCenter database when a virtual machine is deleted or removed from vCenter.

vCenter Server may encounter performance issue during API based access/operation or may report access timeouts

Log/event monitoring tools may report vpxd log spew with ManagedObjectNotFound messages

vpxd logs may rollover faster than expected due to increased logging

/var/log/vmware/vpxd/vpxd.log

yyyy-mm-ddThh:mm:ss error vpxd[51116] [Originator@6876 sub=Authorize opID=75e4d8f3-1f75-4e00-a47e-b02dc8c03595 Authz-4e] MoRef: vim.VirtualMachine:vm-<id> not found. Error: N5Vmomi5Fault21ManagedObjectNotFound9ExceptionE(Fault cause: vmodl.fault.ManagedObjectNotFound
yyyy-mm-ddThh:mm:ss error vpxd[60251] [Originator@6876 sub=Authorize opID=284896e0-3a9d-40ea-9604-dc4b21897956 Authz-7f] MoRef: vim.dvs.DistributedVirtualPortgroup:dvportgroup-<id> not found. Error: N5Vmomi5Fault21ManagedObjectNotFound9ExceptionE(Fault cause: vmodl.fault.ManagedObjectNotFound
yyyy-mm-ddThh:mm:ss error vpxd[60251] [Originator@6876 sub=Authorize opID=284896e0-3a9d-40ea-9604-dc4b21897956 Authz-7f] MoRef: vim.StoragePod:group-p<id> not found. Error: N5Vmomi5Fault21ManagedObjectNotFound9ExceptionE(Fault cause: vmodl.fault.ManagedObjectNotFound
yyyy-mm-ddThh:mm:ss error vpxd[60251] [Originator@6876 sub=Authorize opID=284896e0-3a9d-40ea-9604-dc4b21897956 Authz-7f] MoRef: vim.ClusterComputeResource:domain-c<id> not found. Error: N5Vmomi5Fault21ManagedObjectNotFound9ExceptionE(Fault cause: vmodl.fault.ManagedObjectNotFound
yyyy-mm-ddThh:mm:ss error vpxd[7FB3F3AF6700] [Originator@6876 sub=Authorize opID=d2cea85c-3503-4e00-9c2a-31189f78976d Authz-4] MoRef: vim.HostSystem:host-<id> not found. Error: N5Vmomi5Fault21ManagedObjectNotFound9ExceptionE(vmodl.fault.ManagedObjectNotFound)
yyyy-mm-ddThh:mm:ss error vpxd[48210] [Originator@6876 sub=Authorize opID=3a5e5f83-44] MoRef: vim.Datastore:datastore-<id> not found. Error: N5Vmomi5Fault21ManagedObjectNotFound9ExceptionE(Fault cause: vmodl.fault.ManagedObjectNotFound
yyyy-mm-ddThh:mm:ss error vpxd[11809] [Originator@6876 sub=Authorize opID=81d8358b-01a1-46e3-a2be-b836972aecb4 Authz-4f] MoRef: vim.Datacenter:datacenter-<id> not found. Error: N5Vmomi5Fault21ManagedObjectNotFound9ExceptionE(Fault cause: vmodl.fault.ManagedObjectNotFound

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

This article will provide a method to remove the stale entries for the stale tag associations for the obsolete/deleted objects from vCenter database (vPostgres)

Cause

When a vSphere object (Virtual Machine, Host, Datastore, Distributed portgroup, Datacenter, Cluster, StoragePod) is deleted, the associated tag references are not deleted from cis_kv_keyvalue table of vCenter server database. With vSphere 7.x or later, the tags (created post upgrade/install) for Virtual Machine and Host only are saved under database table vpx_entity_tag_xref and are cleared with the deletion of the object unlike other objects.

Resolution

VMware is aware of this issue and working to resolve this in a future release.

Workaround

Note: Ensure to take a backup or a snapshot of the vCenter Server Appliance before performing this step.

In order to clear the stale associations, proceed with the below steps

Log in to the vCenter server appliance via ssh

Copy the script tags_delete_job_all.sh to a persistent location on the vCenter server appliance via scp. If you have troubles connecting to a vCenter appliance using WinSCP, please see Error when uploading files to vCenter Server Appliance using WinSCP

Change the permission on the script to make the file executable

chmod +x tags_delete_job_all.sh

Execute the script using ./<directory>/tags_delete_job_all.sh

Note: This script does not require a restart of vCenter Server services

In case there is an ask to automate the script, refer to the How to create a cronjob in vCenter Server Appliance 6.x/7.0

Related Information

The deleted information can be found under /var/log/vmware/vpxd-svcs/tagging_cron.log

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

tags_delete_job_all

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant