search cancel

vmware probe stops collecting data from one of the monitored Vcenter

book

Article ID: 209745

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Customer has deployed 3 MCS profiles with vmware monitoring and this is working fine for 2 of them all the time. 

however the following issues are seen for only one of the vcenters:

ISSUE n.1:

•  Intermittently, one of the Vcenters monitored by the vmware probe stops collecting data. A restart of the probe fixes the issue until the next failure. 

•  This issue only happens of one Vcenter. The other 2 monitored continue working fine. 

•  When the issue occurs the following error is seen:

the following is seen in the log when the issue occurrs:

Dec 18 23:43:13:827 [Data Collector - vCenter_, vmware] vCenter_ : inventory update failed.
Dec 18 23:43:13:827 [Data Collector - vCenter_, vmware] java.lang.IllegalArgumentException: Cannot set monitor value for a null monitor definition
 at com.nimsoft.pf.common.Preconditions.checkNotNull(Preconditions.java:28)
 at com.nimsoft.pf.common.ctd.MonitorDefUtils.setMonitorValue(MonitorDefUtils.java:133)
 at com.nimsoft.probe.common.ctd.AbstractInventory.setMetricValue(AbstractInventory.java:265)
 at com.nimsoft.probe.application.vmware.sdk.Inventory.forceUpdateOfHostServices(Inventory.java:711)
 at com.nimsoft.probe.application.vmware.sdk.Inventory.updateArrayMetrics(Inventory.java:660)
 at com.nimsoft.probe.application.vmware.sdk.Inventory.update(Inventory.java:324)
 at com.nimsoft.probe.application.vmware.sdk.VmwareSession.updateInventory(VmwareSession.java:164)
 at com.nimsoft.probe.common.ctd.CtdSession.doInventoryUpdate(CtdSession.java:257)
 at com.nimsoft.probe.application.vmware.collector.VmwareDataCollector.executeSessionUpdateInventory(VmwareDataCollector.java:213)
 at com.nimsoft.probe.common.ctd.ProbeDataCollector.execute(ProbeDataCollector.java:217)
 at com.nimsoft.vm.collector.DataCollector.run(DataCollector.java:151)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:745)

Dec 18 23:43:13:827 [Data Collector - vCenter_EMEA, vmware] PERF: DONE:  Vmware inventory update for vCenter_  {Seconds=1.656}
Dec 18 23:43:13:827 [Data Collector - vCenter_EMEA, vmware] vmware inventory alarm update started
Dec 18 23:43:13:827 [Data Collector - vCenter_EMEA, vmware] Inventory update failed. Sending resource alarm
Dec 18 23:43:13:827 [Data Collector - vCenter_EMEA, vmware] java.lang.IllegalArgumentException: Attempting to add relationship that already exists. 
 at com.nimsoft.ids.ctd.graph.CtdGraphBase.addRelationship(CtdGraphBase.java:281)
 at com.nimsoft.ids.ctd.graph.CtdGraphProbeConfiguration.addRelationship(CtdGraphProbeConfiguration.java:426)
 at com.nimsoft.pf.common.graph.GraphHelper.addPrivateRelationship(GraphHelper.java:744)
 at com.nimsoft.probe.application.vmware.sdk.Inventory.addAlarm(Inventory.java:1339)
 at com.nimsoft.probe.application.vmware.sdk.Inventory.updateAlarms(Inventory.java:1252)
 at com.nimsoft.probe.application.vmware.sdk.VmwareSession.updateInventory(VmwareSession.java:165)
 at com.nimsoft.probe.common.ctd.CtdSession.doInventoryUpdate(CtdSession.java:257)
 at com.nimsoft.probe.application.vmware.collector.VmwareDataCollector.executeSessionUpdateInventory(VmwareDataCollector.java:213)
 at com.nimsoft.probe.common.ctd.ProbeDataCollector.execute(ProbeDataCollector.java:217)
 at com.nimsoft.vm.collector.DataCollector.run(DataCollector.java:151)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:745)

ISSUE n.2:

•  an other behavior seen is that the probe starts collecting the same value over and over (instead of stopping gathering values). A restart of the probe fixes the issue until the next failure as well. 

Environment

Release : 20.x

Component : UIM - VMWARE 7.15

 

Resolution

Provide a downgrade/regression hotfix 7.14HF3 that resolved theses issues or update to vmware 7.16HF4.

Attachments

vmware-7.1.6T4_1656602569607.zip get_app
vmware-7.1.4-HF3 (1)_1619941986614.zip get_app