Lack of data when using Store&Forward with MQTT transmission

Ignition
1

Hi. We’re performing some tests with MQTT transmissions and Store&Forward on 7.9.12 (both server and edge). We’re setting the Edge offline and checking the backlog is sent to the server when it’s back online, and everything seems ok.

Unfortunately it occasionally happens that missing data is not sent. We managed to catch such a case, we checked the logs but all we could find is the excerpt below on the edge. We found nothing related on the Ignition server.

Also, if I got it correctly, the Edge has sent the missing values to the MQTT server. But we had a live plotted graph with the tag values and we didn’t see them.

Where else I can check what’s going on, where are those values gone? Thanks

INFO   | jvm 1    | 2019/07/29 16:06:37 | I [c.c.c.c.CirrusClient          ] [16:06:37]: TransmissionClient-9de44e9d-3c2a-4dea: connect succeeded
INFO   | jvm 1    | 2019/07/29 16:06:37 | I [c.c.c.c.CirrusClient          ] [16:06:37]: TransmissionClient-9de44e9d-3c2a-4dea: Connected to ssl://postman.cloudmqtt.com:20615
INFO   | jvm 1    | 2019/07/29 16:06:37 | W [c.c.m.t.g.m.EdgeNode          ] [16:06:37]: Failed to publish - client is not connected to primary host
INFO   | jvm 1    | 2019/07/29 16:06:37 | I [c.c.m.t.g.m.EdgeNode          ] [16:06:37]: [20190729][TransmissionClient-9de44e9d-3c2a-4dea] Connected to the MQTT Server
INFO   | jvm 1    | 2019/07/29 16:06:37 | I [c.c.m.t.g.TargetCallback      ] [16:06:37]: Got STATE message: STATE/cieHostID :: ONLINE
INFO   | jvm 1    | 2019/07/29 16:06:37 | I [c.c.m.t.g.m.EdgeNode          ] [16:06:37]: Critical/Primary app is ONLINE - cancelling disconnect timer
INFO   | jvm 1    | 2019/07/29 16:06:37 | I [c.c.m.t.g.m.EdgeNode          ] [16:06:37]: [STATE CHANGE] Handling transition to online
INFO   | jvm 1    | 2019/07/29 16:06:38 | E [c.c.m.t.g.m.EdgeNode          ] [16:06:37]: Payload failed to publish - decrementing sequence number
INFO   | jvm 1    | 2019/07/29 16:06:47 | I [c.c.m.t.g.m.EdgeNode          ] [16:06:47]: Processing Rebirth request
INFO   | jvm 1    | 2019/07/29 16:06:48 | I [c.c.m.t.g.h.HistoryPublisher  ] [16:06:47]: Publishing 762 historical metrics to dev02/20190729
INFO   | jvm 1    | 2019/07/29 16:06:48 | W [c.c.m.t.g.m.EdgeNode          ] [16:06:48]: Birth in progress, rescheduling publish task com.cirruslink.mqtt.transmission.gateway.model.EdgeNode$NodePublishDelayTask@14ae6eb
INFO   | jvm 1    | 2019/07/29 16:06:49 | I [c.c.m.t.g.m.EdgeNode          ] [16:06:49]: Rebirth request but just issued a rebirth - ignoring
INFO   | jvm 1    | 2019/07/29 16:06:51 | I [c.c.m.t.g.m.EdgeNode          ] [16:06:51]: Rebirth request but just issued a rebirth - ignoring
INFO   | jvm 1    | 2019/07/29 16:06:56 | I [c.c.m.t.g.m.EdgeNode          ] [16:06:56]: Processing Rebirth request
2

We made some more tests today by disconnecting ethernet cable to two devices, an Arm and an Intel, and both sometimes don’t recover the missing data collected during the offline period.

3

Lorenzo, did you ever figure out what was happening or how to resolve this issue?

4

Unfortunately no. I can’t recall exactly but we likely changed transmission method or even technology.