Hello, I have some issues with my RBOOM, its connected to the network and I can RSH to it, ping it etc but it does not appear to connect to the server or send much data, I have the logs but don’t know how to read them. I am using RSUDP on a server on the same network and it doesn’t seem to connect although setup to connect. This all used to work flawlessly up until about a month or so ago, even though nothing really has changed.
1 Like
SLarchive log:
Fri Jun 10 02:15:55 2022 - network timeout (900s), reconnecting in 30s
Fri Jun 10 02:31:26 2022 - network timeout (900s), reconnecting in 30s
Fri Jun 10 02:46:57 2022 - network timeout (900s), reconnecting in 30s
Fri Jun 10 03:02:27 2022 - network timeout (900s), reconnecting in 30s
Fri Jun 10 03:17:58 2022 - network timeout (900s), reconnecting in 30s
Fri Jun 10 03:33:29 2022 - network timeout (900s), reconnecting in 30s
Fri Jun 10 03:49:00 2022 - network timeout (900s), reconnecting in 30s
Fri Jun 10 04:04:30 2022 - network timeout (900s), reconnecting in 30s
odf_SL_plugin_warn:
| 2022 160 04:30:15>> | DP send to DDS server failed, cannot requeue, queue is full (369865 messages) |
|---|---|
| 2022 160 04:33:39>> | DP send to DDS server failed, cannot requeue, queue is full (369865 messages) |
| 2022 160 04:34:17>> | DP send to DDS server failed, cannot requeue, queue is full (369864 messages) |
| 2022 160 04:35:07>> | DP send to DDS server failed, cannot requeue, queue is full (369863 messages) |
| 2022 160 04:35:27>> | DP send to DDS server failed, cannot requeue, queue is full (369862 messages) |
| 2022 160 04:38:36>> | DP send to DDS server failed, cannot requeue, queue is full (369861 messages) |
| 2022 160 04:39:00>> | DP send to DDS server failed, cannot requeue, queue is full (369860 messages) |
| 2022 160 04:39:25>> | DP send to DDS server failed, cannot requeue, queue is full (369859 messages) |
| 2022 160 04:42:47>> | DP send to DDS server failed, cannot requeue, queue is full (369858 messages) |
| 2022 160 04:43:15>> | DP send to DDS server failed, cannot requeue, queue is full (369858 messages) |
| 2022 160 04:44:03>> | DP send to DDS server failed, cannot requeue, queue is full (369857 messages) |
odf_sl_plugin.err:
2022 161 04:17:52>> ! Q
2022 161 04:17:52>> 1ÑãWDDI–àe†AgMźOkàM&ÑQ’TI I]ä’ïU’QA
2022 161 04:17:52>> 16370 27
2022 161 04:17:58>> internal error: buffer overflow! cannot process read data…
2022 161 04:17:58>> buf:
2022 161 04:17:58>> X†ÅÑEúJ]ä‰L]™
2022 161 04:17:58>> AA∫EBaÉa‡FE
2022 161 04:17:58>> Yàîà ‘U≤U
2022 161 04:17:58>> Yàîc†cTBSTBeî…∆‚ÅEIIãULÅEî…ÀLDI …ÀëeEBeîŸ F
2022 161 04:17:58>> äW†ë[EBWeëE—DŸgEBeURW‚ÅUUUIE´Q—ëEúÅUMUIH´Uõ
2022 161 04:17:58>> 5U†¡SãU™Y!ÅE%ÅSÅRUlÅU!UI¿àE
2022 161 04:17:58>> Y.îò™eíBUã
2022 161 04:17:58>> çHYòE
2022 161 04:17:58>> *%— AÜFEY Ÿ AòDB[ùëE´$ÅWàED™eî…√—ÅEî…À,
2022 161 04:17:58>> 16370 27
2022 161 04:18:05>> internal error: buffer overflow! cannot process read data…
2022 161 04:18:05>> buf: ÅEî… ñe†— AÜFIY Ÿ ÅUíBeîô∆A
2022 161 04:18:05>> Yàîg†¡ÀQWEBeîŸ∂ÃP
2022 161 04:18:05>> YàîVS†¡ÀQÜeTI0…À1äUBeî…∑eëEî…À6%¡ QUHI … ±SUBeî…∆!ÅEî… ïEI … ëQÇReî…∆U
2022 161 04:18:05>> YàîÑU†—nîc†¡ÀQñïTI0…À1SÇBeî…≥‚ëEî…À!TI0…À
2022 161 04:18:05>> 16362 27
2022 161 04:18:11>> internal error: buffer overflow! cannot process read data…
2022 161 04:18:11>> buf: 'DI I]™’îE’AA0JE
2022 161 04:18:11>> X†ÅÑEúJ]ä‰L]™
2022 161 04:18:11>> AA∫EBaÉa–â∆‘U÷™W\FY–ÿU†AaïëEIU
2022 161 04:18:11>> E«+]– U†AaúÅE!EE
2022 161 04:18:11>> !HU
2022 161 04:18:11>> !≈U
2022 161 04:18:11>> !U
2022 161 04:18:11>> !ÑE
2022 161 04:18:11>> 1I™WDHI–à[†AcLÅE1≈E
2022 161 04:18:11>> !D´WDDI–âe†ëQE
2022 161 04:18:11>> QãU Y†ÅQ
2022 161 04:18:11>> SÇBQ´%Ae’ÅEEE
2022 161 04:18:11>> 5SÅBWåDI– [†AcÑÅEƒãW¬FI– S†Ae
2022 161 04:18:11>> EEWÚII–IW†AaçÅE!∆E
2022 161 04:18:11>> [UBQª%AeTÅEED™Q™$ëSLÅUUEºOkàM∏≤ÑQ’TI I]ä’ïU’QA
2022 161 04:18:11>> 16377 27
I am wondering if this is a local UDP issue as TCP seems to be fine…
I will use rs-packetloss on rsudp machine to monitor what’s happening and report back.
just seen this in the odf_SL_plugin.err log:
This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:13>> sendDClientDP(): Error sending data …
2022 161 05:17:13>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:13>> sendDClientDP(): Error sending data …
2022 161 05:17:13>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:13>> sendDClientDP(): Error sending data …
2022 161 05:17:13>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:13>> sendDClientDP(): Error sending data …
2022 161 05:17:13>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:13>> sendDClientDP(): Error sending data …
2022 161 05:17:13>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:13>> sendDClientDP(): Error sending data …
2022 161 05:17:13>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:13>> sendDClientDP(): Error sending data …
2022 161 05:17:13>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:14>> sendDClientDP(): Error sending data …
2022 161 05:17:14>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:14>> sendDClientDP(): Error sending data …
2022 161 05:17:14>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:14>> sendDClientDP(): Error sending data …
2022 161 05:17:14>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:14>> sendDClientDP(): Error sending data …
2022 161 05:17:14>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:14>> sendDClientDP(): Error sending data …
2022 161 05:17:14>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:14>> sendDClientDP(): Error sending data …
2022 161 05:17:14>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:14>> sendDClientDP(): Error sending data …
2022 161 05:17:14>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:14>> sendDClientDP(): Error sending data …
2022 161 05:17:14>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:15>> sendDClientDP(): Error sending data …
2022 161 05:17:15>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:15>> sendDClientDP(): Error sending data …
2022 161 05:17:15>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:15>> sendDClientDP(): Error sending data …
2022 161 05:17:15>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:15>> sendDClientDP(): Error sending data …
2022 161 05:17:15>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:15>> sendDClientDP(): Error sending data …
2022 161 05:17:15>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:15>> sendDClientDP(): Error sending data …
2022 161 05:17:15>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:15>> sendDClientDP(): Error sending data …
2022 161 05:17:15>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:15>> sendDClientDP(): Error sending data …
2022 161 05:17:15>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:16>> sendDClientDP(): Error sending data …
2022 161 05:17:16>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:16>> sendDClientDP(): Error sending data …
2022 161 05:17:16>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:16>> sendDClientDP(): Error sending data …
2022 161 05:17:16>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:16>> sendDClientDP(): Error sending data …
2022 161 05:17:16>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:16>> sendDClientDP(): Error sending data …
2022 161 05:17:16>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:16>> sendDClientDP(): Error sending data …
2022 161 05:17:16>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:16>> sendDClientDP(): Error sending data …
2022 161 05:17:16>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:16>> sendDClientDP(): Error sending data …
2022 161 05:17:16>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:17>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:17>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:17>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:17>> Connection request (raspberryshakedata.com:55555) failed with error code: Connection refused
2022 161 05:17:17>> sendDClientDP(): Error sending data …
2022 161 05:17:17>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:17>> sendDClientDP(): Error sending data …
2022 161 05:17:17>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:17>> sendDClientDP(): Error sending data …
2022 161 05:17:17>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:17>> sendDClientDP(): Error sending data …
2022 161 05:17:17>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:17>> sendDClientDP(): Error sending data …
2022 161 05:17:17>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:18>> sendDClientDP(): Error sending data …
2022 161 05:17:18>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:18>> sendDClientDP(): Error sending data …
2022 161 05:17:18>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:18>> sendDClientDP(): Error sending data …
2022 161 05:17:18>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:18>> sendDClientDP(): Error sending data …
2022 161 05:17:18>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:18>> sendDClientDP(): Error sending data …
2022 161 05:17:18>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:18>> sendDClientDP(): Error sending data …
2022 161 05:17:18>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:18>> internal error: buffer overflow! cannot process read data…
2022 161 05:17:18>> buf: {ˇOk®\u≥âS27Q†ÅÀîQ–E
2022 161 05:17:18>> 'QA
2022 161 05:17:18>> 16224 229
2022 161 05:17:18>> sendDClientDP(): Error sending data …
2022 161 05:17:18>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:18>> sendDClientDP(): Error sending data …
2022 161 05:17:18>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:19>> sendDClientDP(): Error sending data …
2022 161 05:17:19>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:19>> sendDClientDP(): Error sending data …
2022 161 05:17:19>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:19>> sendDClientDP(): Error sending data …
2022 161 05:17:19>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:19>> sendDClientDP(): Error sending data …
2022 161 05:17:19>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:19>> sendDClientDP(): Error sending data …
2022 161 05:17:19>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:19>> sendDClientDP(): Error sending data …
2022 161 05:17:19>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:19>> sendDClientDP(): Error sending data …
2022 161 05:17:19>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:19>> sendDClientDP(): Error sending data …
2022 161 05:17:19>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:20>> sendDClientDP(): Error sending data …
2022 161 05:17:20>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:20>> sendDClientDP(): Error sending data …
2022 161 05:17:20>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:20>> sendDClientDP(): Error sending data …
2022 161 05:17:20>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:20>> sendDClientDP(): Error sending data …
2022 161 05:17:20>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:20>> sendDClientDP(): Error sending data …
2022 161 05:17:20>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:20>> sendDClientDP(): Error sending data …
2022 161 05:17:20>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:20>> sendDClientDP(): Error sending data …
2022 161 05:17:20>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:20>> sendDClientDP(): Error sending data …
2022 161 05:17:20>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:21>> sendDClientDP(): Error sending data …
2022 161 05:17:21>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:21>> sendDClientDP(): Error sending data …
2022 161 05:17:21>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:21>> sendDClientDP(): Error sending data …
2022 161 05:17:21>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:21>> sendDClientDP(): Error sending data …
2022 161 05:17:21>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:21>> sendDClientDP(): Error sending data …
2022 161 05:17:21>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:21>> sendDClientDP(): Error sending data …
2022 161 05:17:21>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:21>> sendDClientDP(): Error sending data …
2022 161 05:17:21>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:21>> sendDClientDP(): Error sending data …
2022 161 05:17:21>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:22>> sendDClientDP(): Error sending data …
2022 161 05:17:22>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:22>> sendDClientDP(): Error sending data …
2022 161 05:17:22>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:22>> sendDClientDP(): Error sending data …
2022 161 05:17:22>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:22>> sendDClientDP(): Error sending data …
2022 161 05:17:22>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:22>> sendDClientDP(): Error sending data …
2022 161 05:17:22>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:22>> sendDClientDP(): Error sending data …
2022 161 05:17:22>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:22>> sendDClientDP(): Error sending data …
2022 161 05:17:22>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:22>> sendDClientDP(): Error sending data …
2022 161 05:17:22>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:23>> sendDClientDP(): Error sending data …
2022 161 05:17:23>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:23>> sendDClientDP(): Error sending data …
2022 161 05:17:23>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:23>> sendDClientDP(): Error sending data …
2022 161 05:17:23>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:23>> sendDClientDP(): Error sending data …
2022 161 05:17:23>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:23>> sendDClientDP(): Error sending data …
2022 161 05:17:23>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:23>> sendDClientDP(): Error sending data …
2022 161 05:17:23>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:23>> sendDClientDP(): Error sending data …
2022 161 05:17:23>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:23>> sendDClientDP(): Error sending data …
2022 161 05:17:23>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:24>> sendDClientDP(): Error sending data …
2022 161 05:17:24>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:24>> sendDClientDP(): Error sending data …
2022 161 05:17:24>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:24>> sendDClientDP(): Error sending data …
2022 161 05:17:24>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:24>> sendDClientDP(): Error sending data …
2022 161 05:17:24>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:24>> sendDClientDP(): Error sending data …
2022 161 05:17:24>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:24>> sendDClientDP(): Error sending data …
2022 161 05:17:24>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:24>> sendDClientDP(): Error sending data …
2022 161 05:17:24>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:24>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:24>> sendDClientDP(): Error sending data …
2022 161 05:17:25>> sendDClientDP(): Error sending data …
2022 161 05:17:25>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:25>> sendDClientDP(): Error sending data …
2022 161 05:17:25>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:25>> sendDClientDP(): Error sending data …
2022 161 05:17:25>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:25>> sendDClientDP(): Error sending data …
2022 161 05:17:25>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:25>> sendDClientDP(): Error sending data …
2022 161 05:17:25>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:25>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:25>> sendDClientDP(): Error sending data …
2022 161 05:17:25>> sendDClientDP(): Error sending data …
2022 161 05:17:25>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:25>> sendDClientDP(): Error sending data …
2022 161 05:17:25>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:26>> sendDClientDP(): Error sending data …
2022 161 05:17:26>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:26>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:26>> sendDClientDP(): Error sending data …
2022 161 05:17:26>> internal error: buffer overflow! cannot process read data…
2022 161 05:17:26>> buf: E
2022 161 05:17:26>> åE
2022 161 05:17:26>> ‘ÅRSª$g»
2022 161 05:17:26>> YäD e†Yª
2022 161 05:17:26>> UUBU $AUMźOk3I] ûUª%ëŒÑA˙ˇOkà
2022 161 05:17:26>> ]∏¢ÑQ˛E
2022 161 05:17:26>> Y†ÅMäîK]ä+ïEúAAÎúJ]ä‰,Y‡ÑEAA∫EBaɇ…U†ëaåÅEeE
2022 161 05:17:26>> W™TW†AQ’ëEcURWeÇBW“FI‡W†ÅWúÅEÖ E
2022 161 05:17:26>> äYUBS$Åe∏
2022 161 05:17:26>> T§+\‡[†Ac“ëE¡™WïUI–U†QYe†A„âE
2022 161 05:17:26>> UTBQe%ÅeïÅEç™QçHI–I™‘U¡X™W¡EY¿U†Ae+
2022 161 05:17:26>> 5¨ëBWïTI–â´‘UMôE
2022 161 05:17:26>> 5aURQUH’ÅS
2022 161 05:17:26>> TWëBWåVI–Öß‘U—™UII¿H¶‘E1E
2022 161 05:17:26>> ÒÑ´WúII‡D´Ù‹Ok®M®≤îQ’TY Y]ä’îU’QA
2022 161 05:17:26>> 16329 269
2022 161 05:17:26>> sendDClientDP(): Error sending data …
2022 161 05:17:26>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:26>> sendDClientDP(): Error sending data …
2022 161 05:17:26>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:26>> sendDClientDP(): Error sending data …
2022 161 05:17:26>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:26>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:26>> sendDClientDP(): Error sending data …
2022 161 05:17:26>> sendDClientDP(): Error sending data …
2022 161 05:17:26>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:26>> sendDClientDP(): Error sending data …
2022 161 05:17:26>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:27>> sendDClientDP(): Error sending data …
2022 161 05:17:27>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:27>> sendDClientDP(): Error sending data …
2022 161 05:17:27>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:27>> sendDClientDP(): Error sending data …
2022 161 05:17:27>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:27>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:27>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
2022 161 05:17:27>> Data has been successfully received, fatal condition resolved.
2022 161 05:17:27>> Connection request (raspberryshakedata.com:55555) failed with error code: Connection refused
2022 161 05:17:27>> sendDClientDP(): Error sending data …
2022 161 05:17:27>> No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
here is the system report:
System Report: Fri Jun 10 05:17:24 UTC 2022
Versioning
OS Version : Raspbian GNU/Linux 10 (buster)
Kernel version : Linux raspberryshake 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux
Software Version : v0.20
Firmware Version : RSnB-5-4.10
ODF Version : 2020.045
Computer Info
RPi revision : a020d3 (3 Model B+)
ODF Serial Port : /dev/ttyS0
MAC Address : b8:27:eb:8f:9f:0d
UpTime : 05:17:24 up 15:20, 1 user, load average: 0.21, 0.14, 0.14
System time : Fri Jun 10 05:17:24 UTC 2022:
Disc usage : /dev/root 7.4G 3.9G 3.3G 54% /
CPU Temp : 79 C
System Info
heli_ewII : Running
OWS : Running
SeedLink : Running
ODF : Running
slarchive : Running
SL info:
AM R9F0D 00 EHZ D 2022/06/09 14:01:46.6890 - 2022/06/10 05:07:22.7540
AM R9F0D 00 HDF D 2022/06/09 14:01:46.6890 - 2022/06/10 05:07:23.1340
crontab Info:
@daily /usr/local/bin/myShake
@hourly /usr/local/bin/clean-logs
10 15 * * 5 /usr/local/bin/rsh-sw-fetcher C >/dev/null 2>&1
Station Info
Data-Sharing Mode : ON
Data Server Conn : ON
Save Data Days : 7
Heli Scale : 0.5
Station Name : AM.R9F0D.00.[EHZ][HDF]
Geophone : OSOP
Clock Info
- ntpdate.service - Network Time Service
Loaded: loaded (/lib/systemd/system/ntpdate.service; enabled; vendor preset: enabled)
Active: active (exited) since Thu 2022-06-09 13:57:54 UTC; 15h ago
Process: 2350 ExecStart=/usr/sbin/ntpd -u ntp:ntp -q -g -x -t 5 (code=exited, status=0/SUCCESS)
Jun 09 13:57:47 raspberryshake ntpd[2350]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jun 09 13:57:47 raspberryshake ntpd[2350]: Listen normally on 2 lo 127.0.0.1:123
Jun 09 13:57:47 raspberryshake ntpd[2350]: Listen normally on 3 eth0 192.168.1.193:123
Jun 09 13:57:47 raspberryshake ntpd[2350]: Listen normally on 4 docker0 172.17.0.2:123
Jun 09 13:57:47 raspberryshake ntpd[2350]: Listen normally on 5 veth0a278ab 169.254.213.208:123
Jun 09 13:57:47 raspberryshake ntpd[2350]: Listening on routing socket on fd #22 for interface updates
Jun 09 13:57:54 raspberryshake ntpd[2350]: ntpd: time slew -0.034650 s
Jun 09 13:57:54 raspberryshake ntpd[2350]: 9 Jun 13:57:54 ntpd[2350]: ntpd: time slew -0.034650 s
Jun 09 13:57:54 raspberryshake ntpd[2350]: ntpd: time slew -0.034650s
Jun 09 13:57:54 raspberryshake systemd[1]: Started Network Time Service.
- ntpd.service - Network Time Service
Loaded: loaded (/lib/systemd/system/ntpd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-06-09 13:57:55 UTC; 15h ago
Process: 3508 ExecStart=/usr/sbin/ntpd -u ntp:ntp -f /etc/ntp.conf -p /run/ntpd.pid (code=exited, status=0/SUCCESS)
Main PID: 3510 (ntpd)
Tasks: 2 (limit: 2059)
CGroup: /system.slice/ntpd.service
`-3510 /usr/sbin/ntpd -u ntp:ntp -f /etc/ntp.conf -p /run/ntpd.pid
Jun 10 04:59:06 raspberryshake ntpd[3510]: new interface(s) found: waking up resolver
Jun 10 05:00:42 raspberryshake ntpd[3510]: Deleting interface #22 eth0, 192.168.1.193#123, interface stats: received=3, sent=3, dropped=0, active_time=96 secs
Jun 10 05:00:42 raspberryshake ntpd[3510]: 162.159.200.123 local addr 192.168.1.193 ->
Jun 10 05:00:42 raspberryshake ntpd[3510]: 178.128.28.21 local addr 192.168.1.193 ->
Jun 10 05:00:42 raspberryshake ntpd[3510]: 203.123.48.219 local addr 192.168.1.193 ->
Jun 10 05:00:53 raspberryshake ntpd[3510]: Listen normally on 23 eth0 192.168.1.193:123
Jun 10 05:00:53 raspberryshake ntpd[3510]: 203.123.48.219 local addr 169.254.213.208 -> 192.168.1.193
Jun 10 05:00:53 raspberryshake ntpd[3510]: 178.128.28.21 local addr 169.254.213.208 -> 192.168.1.193
Jun 10 05:00:53 raspberryshake ntpd[3510]: 162.159.200.123 local addr 169.254.213.208 -> 192.168.1.193
Jun 10 05:00:53 raspberryshake ntpd[3510]: new interface(s) found: waking up resolver
remote refid st t when poll reach delay offset jitter
==============================================================================
SHM(0) .GPS. 0 l - 16 0 0.000 0.000 0.000
SHM(1) .PPS. 0 l - 16 0 0.000 0.000 0.000
+time.cloudflare 10.23.8.4 3 u 256 1024 1 49.575 -47.954 4.293
*178.128.28.21 218.186.3.36 2 u 260 1024 1 44.466 -54.037 9.964
+ntpmon.dcs1.biz 218.186.3.36 2 u 59 1024 7 39.075 -18.781 5.319
Network Info
Stand-Alone Mode : OFF
Ethernet UP : YES
WiFi UP : YES
DNS Available : YES
Network Accessible : YES
Nameservers : 192.168.1.254
=== Shake Data Server ===
Name: raspberryshakedata.com
/usr/local/bin/myShake: line 396: NO: command not found
Port 55555 :
Port 55556 : YES
=== ifconfig =======
docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.17.0.2 netmask 255.255.0.0 broadcast 0.0.0.0
ether 02:42:6a:6e:39:6e txqueuelen 0 (Ethernet)
RX packets 102391 bytes 38249947 (36.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 67679 bytes 10499560 (10.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.193 netmask 255.255.255.0 broadcast 192.168.1.255
ether b8:27:eb:8f:9f:0d txqueuelen 1000 (Ethernet)
RX packets 481732 bytes 99262711 (94.6 MiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 48906 bytes 28643926 (27.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 257 bytes 38166 (37.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 257 bytes 38166 (37.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth2205165: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.206.76 netmask 255.255.0.0 broadcast 169.254.255.255
ether c2:71:27:75:3d:63 txqueuelen 0 (Ethernet)
RX packets 7530 bytes 472878 (461.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8267 bytes 2637920 (2.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth0175f19: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.172.102 netmask 255.255.0.0 broadcast 169.254.255.255
ether ce:b9:a8:62:63:3b txqueuelen 0 (Ethernet)
RX packets 72114 bytes 19846820 (18.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 40116 bytes 6390500 (6.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth0a278ab: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.213.208 netmask 255.255.0.0 broadcast 169.254.255.255
ether f6:5f:65:26:e8:7b txqueuelen 0 (Ethernet)
RX packets 22722 bytes 19361341 (18.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 23744 bytes 2751866 (2.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
===== END ========
=== /etc/network/interfaces FILE ==========
interfaces(5) file used by ifup(8) and ifdown(8)
Please note that this file is written to be used with dhcpcd
For static IP, consult /etc/dhcpcd.conf and ‘man dhcpcd.conf’
Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
auto lo
iface lo inet loopback
iface eth0 inet manual
Start wlan0 definition
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
===== END ========
WiFi Info
Kernel modules loaded : NO
Enablement : OFF
Bluetooth Info
Kernel modules loaded : YES
State : active
Enablement : disabled
Docker Info
Docker version 1.11.1, build 5604cbe
IMAGE ID CREATED AT SIZE REPOSITORY
93374cd693bd 2021-09-17 20:39:31 +0000 UTC 95.46 MB registry.gitlab.com/rshake-public/rsh-fe-config
7b20e90e6a6a 2020-02-14 13:25:56 +0000 UTC 159.5 MB registry.gitlab.com/rshake-public/rsh-data-producer
79f3943a55c6 2019-01-30 19:16:42 +0000 UTC 140.8 MB registry.gitlab.com/rshake-public/rsh-fe-config
992d3d7c940f 2017-06-10 16:40:10 +0000 UTC 144.8 MB registry.gitlab.com/rshake-public/rsh-data-consumer
CONTAINER STATUS CREATED AT
registry.gitlab.com/rshake-public/rsh-data-consumer Up 15 hours 2022-06-09 13:58:02 +0000 UTC
registry.gitlab.com/rshake-public/rsh-data-producer Up 15 hours 2022-06-09 13:57:59 +0000 UTC
registry.gitlab.com/rshake-public/rsh-fe-config:v19 Up 15 hours 2022-06-09 13:56:58 +0000 UTC
Hello clubber1966,
Thak you for contacting us about this issue that you are experiencing.
It appears to be some kind of communication problem, however, without the full logs, I cannot be sure of it. Could you please download all the logs from the /opt/log folder inside the Shake, zip them, and attach them to your answer here on the forum?
Or, in an easier way, if you can access your Shake via IP address or rs.local/, can you please download the zip file from the orange button at the end of the main page, and attach it?
Thank you.
Hello clubber,
Thank you for the complete logs. From them, it appears that there have been some connection problems, but not dependent on the Shake (most likely from your local internet).
However, now they seem to have been solved, because I can see your unit live streaming data to our services, here: RS StationView
If you need anything else in the future, I remain available.