Page History

...

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

...

If we can see in the logs that the MQTT broker is continually forcefully disconnecting an existing connection to allow another client with the same Client ID to connect, as shown below, you have Colliding Client IDs. If not, we have a Colliding Edge Node Descriptors issue.

The logging shows both the Client Id and the associated IP addresses.

If running MQTT Distributor 4.0.13 or earlier, set the debug level for the io.moquette.spi.impl.ProtocolProcessor logger to TRACE and set the filter of the Logs view to ProtocolProcessor.

If running MQTT Distributor 4.0.14 or later, logging will come out as warnings for the com.cirruslink.chariot.server.core.PacketHandler logger.

Image Added

Anchor
ResolvingCollidingClientID ResolvingCollidingClientID

Resolving Colliding Client ID

...

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

...