Running firmware TRB1_R_00.07.08.2
I want to make sure MODBUS data that was read while there was no internet connection is re-sent.
To do this I tried the Retry function under IoT hub collection configuration with Retry count value of 10 and Timeout vakue of 60. This should cover 10 minutes of connection loss.
Simulated no connection. After connection was re-established data was NOT re-sent.
Only after disabling retry and restarting. Below a snippet from Troubleshoot system log:
Mon Sep 2 10:56:17 2024 kern.notice kernel: User “admin” changed modbus_client configuration
Mon Sep 2 10:59:49 2024 user.notice qmux_track: Connection lost.
Mon Sep 2 11:00:27 2024 kern.notice IPv4 connectivity started to fail
Mon Sep 2 11:01:16 2024 daemon.err data_sender: Method ‘message’ returned an error (err_no: 2)
Mon Sep 2 11:02:00 2024 kern.notice DNS resolution started to fail
Mon Sep 2 11:02:17 2024 daemon.err data_sender: Method ‘message’ returned an error (err_no: 2)
Mon Sep 2 11:03:17 2024 daemon.err data_sender: Method ‘message’ returned an error (err_no: 2)
Mon Sep 2 11:03:25 2024 kern.notice DNS resolution restored
Mon Sep 2 11:04:25 2024 kern.notice IPv4 connectivity restored
Mon Sep 2 11:07:14 2024 daemon.info mobifd: [gsm.modem0] Low signal notify triggered! Signal: “-93” | Threshold: “-90”
Mon Sep 2 11:12:37 2024 kern.notice kernel: User “admin” changed data_sender configuration
Mon Sep 2 11:12:39 2024 daemon.notice data_sender: Signal received, exiting
Mon Sep 2 11:12:39 2024 daemon.err data_sender: Option ‘retry_timeout’ has invalid value ‘60’. Retry timeout in seconds [1, 10]
Mon Sep 2 11:12:39 2024 daemon.err data_sender: Error while parsing config section ‘1’
Mon Sep 2 11:12:59 2024 kern.notice IPv4 connectivity started to fail
Mon Sep 2 11:13:11 2024 user.notice qmux_track: Connection lost.
Mon Sep 2 11:14:32 2024 kern.notice DNS resolution started to fail
Mon Sep 2 11:18:33 2024 kern.notice IPv4 connectivity restored
Mon Sep 2 11:18:36 2024 kern.notice DNS resolution restored
Mon Sep 2 11:31:52 2024 kern.notice kernel: User “admin” changed data_sender configuration
Mon Sep 2 11:31:53 2024 daemon.notice data_sender: Signal received, exiting
Mon Sep 2 11:32:54 2024 daemon.err data_sender: Method ‘message’ returned an error (err_no: 4)
Mon Sep 2 11:41:07 2024 daemon.notice netifd: mob1s1a1_4 (6630): udhcpc: broadcasting renew
Mon Sep 2 11:41:35 2024 user.notice qmux_track: Connection lost.
Mon Sep 2 11:41:51 2024 kern.notice IPv4 connectivity started to fail
Mon Sep 2 11:42:04 2024 daemon.err data_sender: Method ‘message’ returned an error (err_no: 2)
Mon Sep 2 11:42:14 2024 daemon.err data_sender: Method ‘message’ returned an error (err_no: 2)
Mon Sep 2 11:42:24 2024 daemon.err data_sender: Method ‘message’ returned an error (err_no: 2)
It seems retry timeout of value has a max value of 10 (shows 60 when hovering over de data field during configuration).
Can this be fixed or is there another way to cover connection loss?