Docker_Monitor. - Attempting to add vertex that already exists.id alarm

Document ID : KB000124154
Last Modified Date : 07/01/2019
Show Technical Document Details
Issue:
Sporadic get alarms like: 

prd7867.smt.tchile.local is not responding (reason: Connection and/or inventory update failure) {Attempting to add vertex that already exists.id: '/Domain/XXXXX/YYYYY/docker_monitor:idsProbe:Gamification::Hosts::YYYYY::Containers::CONTAINER000-dashboard:movistar-dashboard:4.4::Processes:.CtdDisplayAttribute'}

At log we can see entries like:
...
....
Nov 21 22:07:56:918 [Data Collector - CONTAINER000, docker_monitor] Inventory update failed. Sending resource alarm
Nov 21 22:07:56:919 [Data Collector - CONTAINER000, docker_monitor] (1) error, Inventory update failed for CONTAINER000: Attempting to add vertex that already exists.id: '/Domain/XXXXX/YYYYY/docker_monitor:idsProbe:CONTAINER000::Hosts::YYYYY::Containers::CONTAINER000-api-v2-3:registry-default.infra.preprod.ocp.tchile.local/tcl-registry/movistar-api-v2:16.1::Processes:.CtdDisplayAttribute'
    at com.nimsoft.probe.framework.genprobe.GenInventory.handleInventoryUpdateException(GenInventory.java:202) .......
Caused by: java.lang.IllegalArgumentException: Attempting to add vertex that already exists.id: '/Domain/XXXXX/YYYYY/docker_monitor:idsProbe:CONTAINER000::Hosts::YYYYY::Containers::CONTAINER000-api-v2-3:registry-default.infra.preprod.ocp.tchile.local/tcl-registry/movistar-api-v2:16.1::Processes:.CtdDisplayAttribute'
    at tgraph2.TGraph2.addVertex(TGraph2.java:43) ....
Nov 21 22:07:56:919 [Data Collector - CONTAINER000, docker_monitor] for remote probe, getResourceAlarm is using Resource Generated Device Id: 2393aab26c44f6dd665260094dcec671
Nov 21 22:07:56:919 [Data Collector - CONTAINER000, docker_monitor] for remote probe, getResourceAlarm is using Resource Generated Device Id: 2393aab26c44f6dd665260094dcec671
Nov 21 22:07:56:919 [Data Collector - CONTAINER000, docker_monitor] PERF: DONE:  ----- Pass-078 --- Data Collector Check Interval for: CONTAINER000   {Seconds=0.309}
Nov 21 22:07:56:919 [Data Collector - CONTAINER000, docker_monitor] PERF: Memory Status: Max=1820   CurrentAllocated=52   Free=22   Used=30 MB
Nov 21 22:07:56:919 [Data Collector - CONTAINER000, docker_monitor] DataCollector for CONTAINER000 finished collecting data
Nov 21 22:07:57:919 [BulkSender Monitor, docker_monitor] Bulk send 2 alarms
Nov 21 22:07:57:921 [BulkSender Monitor, docker_monitor] Sent NimAlarm C, severity=5, message==YYYYY.smt.tchile.local is not responding (reason: Connection and/or inventory update failure) {Attempting to add vertex that already exists.id: '/Domain/XXXXX/YYYYY/docker_monitor:idsProbe:CONTAINER000::Hosts::YYYYY::Containers::CONTAINER000-api-v2-3:registry-default.infra.preprod.ocp.tchile.local/tcl-registry/movistar-api-v2:16.1::Processes:.CtdDisplayAttribute'}, subsystem=2.23, suppressionid=CONTAINER000, source=YYYYY and received confirmation id NA56926375-06629
Nov 21 22:07:57:921 [BulkSender Monitor, docker_monitor] Sent NimAlarm D, severity=5, message==YYYYY.smt.tchile.local is not responding (reason: Connection and/or inventory update failure) {Attempting to add vertex that already exists.id: '/Domain/XXXXX/YYYYY/docker_monitor:idsProbe:CONTAINER000::Hosts::YYYYY::Containers::CONTAINER000-api-v2-3:registry-default.infra.preprod.ocp.tchile.local/tcl-registry/movistar-api-v2:16.1::Processes:.CtdDisplayAttribute'}, subsystem=2.23, suppressionid=CONTAINER000, source=YYYYY.smt.tchile.local and received confirmation id NA56926375-06630
....
Resolution:
Please follow next steps:

- Open a support ticket to request docker_monitor-1.4.7-T1.zip or updated version 
- Deactivate the docker_monitor probe. 
- Import into archive docker_monitor provided or above 
- Deploy docker_monitor or above to machine that corresponds 
- Activate the docker_monitor probe.