0

MQTT Collector - Error while connecting to broker and logging node data

Trying to connect to an EMQX broker using TCP with SSL enabled. The reconnect interval is 1 minute, followed by Keep Alive 30.
The connection group made with the MQTT Collector in the Canary Admin is configured not to be the Primary Application, using the SparkplugB 2.2 protocol.
Automatically log all tags disabled.

Initially, the tag logging was a success, with 105 tags from Node1 being logged. Upon adding Node2 with 204 tags, the dataset logging was also successful, with a total of 309 tags being logged.

After some adjustments to the data published to the broker, there was an issue with the Node2 connection (logs attached in pdf). The log messages were five consecutively:

  • Received device birth
  • Metadata received but unsupported
  • Received node control metric 'Node Control/ Next Server' with value 'false'
  • Received node control metric 'Node Control/ Rebirth' with value 'false'
  • Received node birth
  • Received device birth (repeats cycle)

After this, logging of Node2 was no longer performed.

Despite these efforts, the issue persists. The machine with the services were restarted, the old connection group in the MQTT Collector was deleted, and a new one with the same properties was created. However, even with these steps, a connection to the broker cannot be established. This situation underscores the need for further investigation and resolution.

 

Thanks in advance. I'm waiting for your response.

2 replies

null
    • john_patanian
    • 1 mth ago
    • Reported - view

    Was this issue ever resolved?   I have a similar issue where I think re-birth message are not getting read and the MQTT collector stops writing.

      • gilbert_delgado
      • 1 mth ago
      • Reported - view

       
      Hello John,
      We later found the issue was that a UDT wasn't being published onto the broker, so the node could not create itself correctly.
      The device sends a birth message but cannot complete the sequence because of the UDT's misconfiguration. Maybe, in your case, there is a bad state tag or UDT that doesn't let the node complete the birth sequence.

Content aside

print this pagePrint this page
  • 1 mth agoLast active
  • 2Replies
  • 28Views
  • 2 Following