- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-30-2020 03:08 AM
Root Cause:
Discovery performed for a Server (Linux/Windows/etc.,), the running processes information of that server is also fetched. Based on the processes information and the classification condition for each process, respective discovery is triggered further.
If the server has the vCenter running then the "vpxd" and "vmware-vpxd-svcs.launcher" could come along with the other processes information then the vCenter discovery triggered and it's based on the vCenter process classification in the "discovery_classy_proc" table.
Due to the above condition, the vCenter discovery is triggered multiple times thereby deleting the duplicate vCenter records as a part of the regular flow.
vCenter process classification condition is: command "contains" vpxd
Please find the attachment.
Solution:
Set the vCenter process classification condition: command "is" vpxd
- 2,507 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
if you use "is" you will not catch cases where the command is actually listed as "vpxd.exe". It may be better to stay with contains, but rule out the junk by adding "and does not contain" "launcher".