The server is not an issue. Even if I’m not getting data from the node, the gateway is still connected to the server and sending heartbeat data.
I’m now trying to see at which temperature the RAK2245 is stoping working correctly.
Do you have datasheet with a description regarding its range of temp?
Thanks.
This temperature shouldn’t matter.
I managed to reduce the temp by having a better air cooling flow. but still having to reboot or relaunch the packet forwarder time to time.
It could be after 1 day, 2 days or few hours.
I can’t find any info in messages or syslog telling me what’s going on when it stops.
I’m lost. I have no more idea except a hardware problem with the RAK2245.
Anything else I could try?
Thanks
I will set up a vpn server during working hours next week. When this problem occurs, I can connect to this RAK7243 through vpn.
Could you leave your email? I will send you the VPN configuration file next week.
Very similar issued happened. Stop receiving packets after sometime and packet forwarder need to be rebooted. Seems like intermittent or slow connection affect somehow the part of the packet forwarder that reads from the radio hardware, but the part that sends “heartbeat” to chirpstack server still works.We moved the server to another place with another internet connection and the problem magically disappeared.
Looking at syslog I have a lot of CRC failed in few minutes.
Packet forwarder is still OK but I’m wondering if this could be the cause.
May 31 16:26:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:27:44 rak-gateway ttn-gateway[486]: # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:27:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:27:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
May 31 16:29:31 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:29:31 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:29:31 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:31:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
May 31 16:31:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:31:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
May 31 16:32:24 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
May 31 16:32:24 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:32:24 rak-gateway ttn-gateway[486]: # CRC_OK: 50.00%, CRC_FAIL: 50.00%, NO_CRC: 0.00%
May 31 16:33:44 rak-gateway ttn-gateway[486]: # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:33:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:33:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:35:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:35:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
May 31 16:35:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:37:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
May 31 16:37:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
May 31 16:37:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
May 31 16:37:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
May 31 16:38:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%
May 31 16:38:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:38:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:40:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:40:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:40:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:41:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:41:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:41:44 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:43:14 rak-gateway ttn-gateway[486]: # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:43:14 rak-gateway ttn-gateway[486]: # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 31 16:43:14 rak-gateway ttn-gateway[486]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
According to the description of mmelo, it is possible that the chirpstack built into the gateway affected lora_pkt_fwd.
Can you try to disable chirpstack?
sudo systemctl disable chirpstack-application-server
sudo systemctl disable chirpstack-gateway-bridge
sudo systemctl disable chirpstack-network-server
sudo systemctl disable redis-server.service
sudo systemctl disable postgresql.service
Restart the gateway to make the configuration take effect.
It seems to be much better by stopping Chirpstack on the gateway.
I have also stopped few nodes as well.
I’m going to restart them and see if there is an impact.
Patrice