search cancel

meraki profile in error state with Cannot add member relationship to null parent node

book

Article ID: 256992

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After creating a profile once the prerequisites have been met, the profile is in an error or failed state, and the log indicates the following:

Dec 29 17:06:22:964 [Data Collector - Profile Meraki, meraki] (1) error, Inventory update failed for Profile Meraki: Cannot add member relationship to null parent node
    at com.nimsoft.probe.framework.genprobe.GenInventory.handleInventoryUpdateException(GenInventory.java:209)
    at com.nimsoft.probe.framework.genprobe.GenInventory.update(GenInventory.java:186)
    at com.nimsoft.probe.framework.genprobe.GenSession.updateInventory(GenSession.java:145)
    at com.nimsoft.probe.common.ctd.CtdSession.doInventoryUpdate(CtdSession.java:258)
    at com.nimsoft.probe.common.ctd.ProbeDataCollector.executeSessionUpdateInventory(ProbeDataCollector.java:1063)
    at com.nimsoft.probe.common.ctd.ProbeDataCollector.execute(ProbeDataCollector.java:218)
    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:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: Cannot add member relationship to null parent node
    at com.nimsoft.pf.common.Preconditions.checkNotNull(Preconditions.java:28)
    at com.nimsoft.pf.common.graph.GraphHelper.checkAddHasChildRelationship(GraphHelper.java:471)
    at com.nimsoft.pf.common.graph.GraphHelper.checkAddHasChildRelationship(GraphHelper.java:493)
    at com.nimsoft.pf.common.graph.GraphHelper.checkAddElement(GraphHelper.java:337)
    at com.nimsoft.pf.common.graph.GraphHelper.checkAddElement(GraphHelper.java:344)
    at com.nimsoft.probe.framework.genprobe.GenInventory.addElementToGraph(GenInventory.java:406)
    at com.nimsoft.probe.framework.genprobe.GenInventory.addNode(GenInventory.java:382)
    at com.nimsoft.probe.framework.genprobe.GenInventory.addItem(GenInventory.java:330)
    at com.nimsoft.probe.framework.genprobe.GenInventory.update(GenInventory.java:138)
    ... 12 more

Environment

Release : 20.4

Component: meraki probe

Resolution

This is due to the fact that Hostname Visibility was recently set for the meraki instance, but it has not had time to propagate completely.

https://documentation.meraki.com/MR/Monitoring_and_Reporting/Hostname_Visibility

Please note per Cisco it can take up to 24 hours for the changes to propagate completely.