MQTT Engine 4.0.35 — continuous rebirth loop, DDATA rejected with unbirthed metric name

Ignition Modules MQTT Modules
1

MQTT Engine is stuck in a rebirth loop on a single Sparkplug edge node. Every ~11.6 seconds it rejects a DDATA message with a sequence number error, requests a rebirth, and the cycle repeats. It has never recovered on its own in over 50 hours — 16,880 rebirth requests logged.

Each cycle logs exactly two SparkplugUtils value-conversion failures. The metric names in those failures are bare (Input/DisableDescriptions), while every one of the 24,989 metrics in the DBIRTH carries a full path. We cannot explain how a DDATA metric arrives under a name that appears in no BIRTH.

2

Hello Tyler,

I would have you open a Support ticket at support@cirrus-link.com

Please report the versions of Ignition and MQTT Engine module (and any modules on that Gateway).

I’ll need the Diagnostic Bundle from the Gateway with Engine. Do you know who the Client is that is publishing these messages? Is it possible there is more than one Client publishing into the same Group/Edge Node?

Who is the Broker?

Please provide the answers to these questions in your email to Support.

Dan