Page History

...

Now we can use the logging associated with your Chariot or MQTT Engine/Distributor instance to determine the physical or virtual Edge Nodes with duplicate Group and Node IDs.

...

Expanding the Failed to handle DDATA message exposes the sequence number error we would expect in this scenario. 

From the Ignition UI connected to your instance of MQTT Distributor, navigate to Status > Diagnostic > Logs.

Set the debug level for the io.moquette.spi.impl.ProtocolProcessor logger to TRACE and in the filter search for the NBIRTH messages for the duplicate Edge Node ID. In this example the filter will be for Lakeside/NBIRTH/Finished Goods. Now we can see which Client IDs are responding to the rebirth requests from MQTT Engine. 

...