"DEBUG: Attempting to (re)connect"
# helpk
koirin
02/07/2023, 2:06 PMAfter my device receives a "DEADLINE_EXCEEDED" error, the device gets stuck in this "DEBUG: Attempting to (re)connect" loop. It won't even reboot. It is set up with an MQTT-connection, and I think this somehow is the cause. How can I fix this?
koirin
02/07/2023, 2:07 PMThe device is pending "reboot", but nothing is happening
f
floitsch
02/07/2023, 3:02 PMHmm.
This looks like the MQTT client is too aggressive in reconnecting.
floitsch
02/07/2023, 3:02 PMThe latest version won't give up.
floitsch
02/07/2023, 3:03 PMIt's interesting that the logs still make it to the server.
floitsch
02/07/2023, 3:03 PMSo the client and server seem to be able to communicate just fine.
floitsch
02/07/2023, 3:04 PMNot sure why the reboot isn't happening, though.
floitsch
02/07/2023, 3:05 PMCould be that there are safe-guards to force the device to recover eventually, but I'm not sure if that will trigger, or at which time that would happen.
k
koirin
02/07/2023, 3:09 PMThe max-offline parameter is set to 30 seconds, but I noticed this loop kept going for 15-20 minutes, dumping data live in the logs, instead of every 30 seconds. Then it just suddenly stopped, logs were frozen for a while, then it shutdown and restarted
koirin
02/07/2023, 3:10 PMAll while the reboot was pending of course
f
floitsch
02/07/2023, 3:17 PMI guess that's good.
floitsch
02/07/2023, 3:17 PMThis means that some watchdog finally triggered
floitsch
02/07/2023, 3:19 PMI have it on my TODO list to improve the MQTT package to make it less aggressive. At the moment I'm busy with other things, but eventually...
7 Views