Gateway connected, but not forwarding data

Gateways Raspberry Pi Gateways
1

Hello together

I’m new to lora and TTn, just building up my first nodes and apps.
As I had no converage where I life, I created a gateway, based on RAK831 and a RPI zero W. The gateway already received and forwarded about 42 packets to TTN and I can see the payload on the console - OK.

For the setup I used: https://github.com/ch2i/LoraGW-Setup

But now after a while, the gateway status is still ‘connected’ in the console, but last seen is ‘25 minutes ago’.
In the RPI console I see it received a RF packet was received by the gateway and was sent to TTN. But I don’t see that packet on the TTN console, neither on the gateway nor on the device… I also restartet the RPI, without success.

What is the way to go to troubleshoot this further?

Below are some logs from my gateway.

Thank you

May 10 02:14:09 loragw loragw[260]: 02:14:09 INFO: [TTN] bridge.eu.thethings.network RTT 52
May 10 02:14:09 loragw loragw[260]: 02:14:09 INFO: [TTN] send status success for bridge.eu.thethings.network
May 10 02:14:09 loragw loragw[260]: 02:14:09 INFO: [up] TTN lora packet send to server “bridge.eu.thethings.network”
May 10 02:14:39 loragw loragw[260]: 02:14:39 INFO: Disabling GPS mode for concentrator’s counter…
May 10 02:14:39 loragw loragw[260]: 02:14:39 INFO: host/sx1301 time offset=(1525911217s:222397µs) - drift=-130µs
May 10 02:14:39 loragw loragw[260]: 02:14:39 INFO: Enabling GPS mode for concentrator’s counter.
May 10 02:14:39 loragw loragw[260]: ##### 2018-05-10 00:14:39 GMT #####
May 10 02:14:39 loragw loragw[260]: ### [UPSTREAM] ###
May 10 02:14:39 loragw loragw[260]: # RF packets received by concentrator: 1
May 10 02:14:39 loragw loragw[260]: # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 10 02:14:39 loragw loragw[260]: # RF packets forwarded: 1 (21 bytes)
May 10 02:14:39 loragw loragw[260]: # PUSH_DATA datagrams sent: 0 (0 bytes)
May 10 02:14:39 loragw loragw[260]: # PUSH_DATA acknowledged: 0.00%
May 10 02:14:39 loragw loragw[260]: ### [DOWNSTREAM] ###
May 10 02:14:39 loragw loragw[260]: # PULL_DATA sent: 0 (0.00% acknowledged)
May 10 02:14:39 loragw loragw[260]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
May 10 02:14:39 loragw loragw[260]: # RF packets sent to concentrator: 0 (0 bytes)
May 10 02:14:39 loragw loragw[260]: # TX errors: 0
May 10 02:14:39 loragw loragw[260]: ### BEACON IS DISABLED!
May 10 02:14:39 loragw loragw[260]: ### [JIT] ###
May 10 02:14:39 loragw loragw[260]: # INFO: JIT queue contains 0 packets.
May 10 02:14:39 loragw loragw[260]: # INFO: JIT queue contains 0 beacons.
May 10 02:14:39 loragw loragw[260]: ### GPS IS DISABLED!
May 10 02:14:39 loragw loragw[260]: ### [PERFORMANCE] ###
May 10 02:14:39 loragw loragw[260]: # Upstream radio packet quality: 100.00%.
May 10 02:14:39 loragw loragw[260]: ### [ CONNECTIONS ] ###
May 10 02:14:39 loragw loragw[260]: # bridge.eu.thethings.network: Connected
May 10 02:14:39 loragw loragw[260]: # Semtech status report send.
May 10 02:14:39 loragw loragw[260]: ##### END #####
May 10 02:14:39 loragw loragw[260]: 02:14:39 INFO: [TTN] bridge.eu.thethings.network RTT 53
May 10 02:14:39 loragw loragw[260]: 02:14:39 INFO: [TTN] send status success for bridge.eu.thethings.network
May 10 02:15:09 loragw loragw[260]: ##### 2018-05-10 00:15:09 GMT #####
May 10 02:15:09 loragw loragw[260]: ### [UPSTREAM] ###
May 10 02:15:09 loragw loragw[260]: # RF packets received by concentrator: 0
May 10 02:15:09 loragw loragw[260]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 10 02:15:09 loragw loragw[260]: # RF packets forwarded: 0 (0 bytes)
May 10 02:15:09 loragw loragw[260]: # PUSH_DATA datagrams sent: 0 (0 bytes)
May 10 02:15:09 loragw loragw[260]: # PUSH_DATA acknowledged: 0.00%
May 10 02:15:09 loragw loragw[260]: ### [DOWNSTREAM] ###
May 10 02:15:09 loragw loragw[260]: # PULL_DATA sent: 0 (0.00% acknowledged)
May 10 02:15:09 loragw loragw[260]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
May 10 02:15:09 loragw loragw[260]: # RF packets sent to concentrator: 0 (0 bytes)
May 10 02:15:09 loragw loragw[260]: # TX errors: 0
May 10 02:15:09 loragw loragw[260]: ### BEACON IS DISABLED!
May 10 02:15:09 loragw loragw[260]: ### [JIT] ###
May 10 02:15:09 loragw loragw[260]: # INFO: JIT queue contains 0 packets.
May 10 02:15:09 loragw loragw[260]: # INFO: JIT queue contains 0 beacons.
May 10 02:15:09 loragw loragw[260]: ### GPS IS DISABLED!
May 10 02:15:09 loragw loragw[260]: ### [PERFORMANCE] ###
May 10 02:15:09 loragw loragw[260]: # Upstream radio packet quality: 0.00%.
May 10 02:15:09 loragw loragw[260]: ### [ CONNECTIONS ] ###
May 10 02:15:09 loragw loragw[260]: # bridge.eu.thethings.network: Connected
May 10 02:15:09 loragw loragw[260]: # Semtech status report send.
May 10 02:15:09 loragw loragw[260]: ##### END #####
May 10 02:15:09 loragw loragw[260]: 02:15:09 INFO: [TTN] bridge.eu.thethings.network RTT 49
May 10 02:15:09 loragw loragw[260]: 02:15:09 INFO: [TTN] send status success for bridge.eu.thethings.network
May 10 02:15:39 loragw loragw[260]: 02:15:39 INFO: Disabling GPS mode for concentrator’s counter…
May 10 02:15:39 loragw loragw[260]: 02:15:39 INFO: host/sx1301 time offset=(1525911217s:222042µs) - drift=-355µs
May 10 02:15:39 loragw loragw[260]: 02:15:39 INFO: Enabling GPS mode for concentrator’s counter.
May 10 02:15:39 loragw loragw[260]: ##### 2018-05-10 00:15:39 GMT #####
May 10 02:15:39 loragw loragw[260]: ### [UPSTREAM] ###
May 10 02:15:39 loragw loragw[260]: # RF packets received by concentrator: 0
May 10 02:15:39 loragw loragw[260]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 10 02:15:39 loragw loragw[260]: # RF packets forwarded: 0 (0 bytes)
May 10 02:15:39 loragw loragw[260]: # PUSH_DATA datagrams sent: 0 (0 bytes)
May 10 02:15:39 loragw loragw[260]: # PUSH_DATA acknowledged: 0.00%
May 10 02:15:39 loragw loragw[260]: ### [DOWNSTREAM] ###
May 10 02:15:39 loragw loragw[260]: # PULL_DATA sent: 0 (0.00% acknowledged)
May 10 02:15:39 loragw loragw[260]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
May 10 02:15:39 loragw loragw[260]: # RF packets sent to concentrator: 0 (0 bytes)
May 10 02:15:39 loragw loragw[260]: # TX errors: 0
May 10 02:15:39 loragw loragw[260]: ### BEACON IS DISABLED!
May 10 02:15:39 loragw loragw[260]: ### [JIT] ###
May 10 02:15:39 loragw loragw[260]: # INFO: JIT queue contains 0 packets.
May 10 02:15:39 loragw loragw[260]: # INFO: JIT queue contains 0 beacons.
May 10 02:15:39 loragw loragw[260]: ### GPS IS DISABLED!
May 10 02:15:39 loragw loragw[260]: ### [PERFORMANCE] ###
May 10 02:15:39 loragw loragw[260]: # Upstream radio packet quality: 0.00%.
May 10 02:15:39 loragw loragw[260]: ### [ CONNECTIONS ] ###
May 10 02:15:39 loragw loragw[260]: # bridge.eu.thethings.network: Connected
May 10 02:15:39 loragw loragw[260]: # Semtech status report send.
May 10 02:15:39 loragw loragw[260]: ##### END #####
May 10 02:15:39 loragw loragw[260]: 02:15:39 INFO: [TTN] bridge.eu.thethings.network RTT 54
May 10 02:15:39 loragw loragw[260]: 02:15:39 INFO: [TTN] send status success for bridge.eu.thethings.network

2

All my monitored gateways using the TTN protocol were ‘off-line’ according to TTN between ~23:50 and ~1:10 UTC last night. It looks like your tests were in that window.

When testing always keep in mind the back-end might have issues.

3

Hello Kersing

Thank you very much for your answer.
I can see that the gateway is working again… strange thin is, on https://status.thethings.network/ is nothing mentioned about the outage… will messages in this time be processed later?
Would the legacy packet forwarder be more stable?

I hope those outages are not coming up daily, it always makes me always uncertainty when testing something and then there is a issue in the first hours or days while testing ;).

Thank you

4

That page is maintained by hand and in my experience these outages are automatically detected and recovered at some point, so when the persons tasked with operations gets back to work (not today as it is a holiday in NL) everything is up and running.

Not if they have not been processed by now. I have seen several kinds of outages:

  1. the connection status was not up to date,
  2. data flow had (severe) delays,
  3. combination of 1 and 2,
  4. no data and status updates.

I my experience not really. For both ways of connecting I’ve seen outages. Some people hedge their bets and connect a gateway both ways (MP forwarder allows this, I am not advising anyone to do so as it increased the load on the back-end)

In my experience the outages certainly do not occur on a daily basis.

5

Thank you very much for explanaition kersing.

As I already encountered again an outage of the packet forwarder using TTN protocol, I switched now shortly to the legacy packet forwarder and this one seems to work fine at the moment.

Have a nice evening