Conduit stopped processing LoRa packets, won't respond to reboot command

[Bob Doiron]

Hi,
We have an AEP Conduit running at a customer’s site that suddenly stopped sending data to us. We use node-red to process LoRa messages from our sensors and push the data to our server using an https post.

The strange part is that the conduit is still checking in to DeviceHQ, but we can’t get it to send any logs or reboot using the DeviceHQ queued commands. Any idea what might cause this behavior?

I noticed in the last successfully retrieved log file package that the app/node-red.log file had grown to 15MB. It doesn’t appear to be a daily rotating log like I expected. Could the filesystem be full? If so, how does one limit the node-red log file size?

Thanks

• This topic was modified 5 years, 9 months ago by Bob Doiron.

[Author]

Posts