ChirpStack Gateway Bridge Config Problem [AWS Ubuntu - RAK7258]

ChirpStack Gateway Bridge
#1

Good day,
I have a problem where my gateway-bridge** where there are errors initially then it connects to the the UDP and MQTT in an unstable way** as seen below:

Here is the actual terminal results:

ubuntu@ip-172-31-41-91 : ~ $ journalctl -u chirpstack-gateway-bridge -f -n 50

– Logs begin at Wed 2020-11-18 23:22:05 UTC. –

Nov 19 00:12:04 ip-172-31-41-91 chirpstack-gateway-bridge[2868]: time=“2020-11-19T00:12:04Z” level=error msg=“integration/mqtt: connection error” error=“Network Error : dial tcp 127.0.0.1:1883: connect: connection refused”

Nov 19 00:12:06 ip-172-31-41-91 chirpstack-gateway-bridge[2868]: time=“2020-11-19T00:12:06Z” level=error msg=“integration/mqtt: connection error” error=“Network Error : dial tcp 127.0.0.1:1883: connect: connection refused”

Nov 19 00:12:08 ip-172-31-41-91 chirpstack-gateway-bridge[2868]: time=“2020-11-19T00:12:08Z” level=error msg=“integration/mqtt: connection error” error=“Network Error : dial tcp 127.0.0.1:1883: connect: connection refused”

Nov 19 00:12:10 ip-172-31-41-91 chirpstack-gateway-bridge[2868]: time=“2020-11-19T00:12:10Z” level=error msg=“integration/mqtt: connection error” error=“Network Error : dial tcp 127.0.0.1:1883: connect: connection refused”

Nov 19 00:13:10 ip-172-31-41-91 chirpstack-gateway-bridge[2868]: time=“2020-11-19T00:13:10Z” level=info msg=“integration/mqtt: connected to mqtt broker”

Nov 19 00:14:03 ip-172-31-41-91 systemd[1]: Stopping ChirpStack Gateway Bridge…

Nov 19 00:14:03 ip-172-31-41-91 chirpstack-gateway-bridge[2868]: time=“2020-11-19T00:14:03Z” level=info msg=“signal received” signal=terminated

Nov 19 00:14:03 ip-172-31-41-91 chirpstack-gateway-bridge[2868]: time=“2020-11-19T00:14:03Z” level=warning msg=“shutting down server”

Nov 19 00:14:03 ip-172-31-41-91 systemd[1]: Stopped ChirpStack Gateway Bridge.

Nov 19 00:14:03 ip-172-31-41-91 systemd[1]: Started ChirpStack Gateway Bridge.

Nov 19 00:14:04 ip-172-31-41-91 chirpstack-gateway-bridge[17796]: time=“2020-11-19T00:14:04Z” level=info msg=“starting ChirpStack Gateway Bridge” docs=“https://www.chirpstack.io/gateway-bridge/” version=3.9.2

Nov 19 00:14:04 ip-172-31-41-91 chirpstack-gateway-bridge[17796]: time=“2020-11-19T00:14:04Z” level=info msg=“backend/semtechudp: starting gateway udp listener” addr=“0.0.0.0:1700”

Nov 19 00:14:04 ip-172-31-41-91 chirpstack-gateway-bridge[17796]: time=“2020-11-19T00:14:04Z” level=info msg=“integration/mqtt: connected to mqtt broker”

> Nov 20 00:30:48 ip-172-31-41-91 systemd[1]: Stopping ChirpStack Gateway Bridge…

Nov 20 00:30:48 ip-172-31-41-91 chirpstack-gateway-bridge[17796]: time=“2020-11-20T00:30:48Z” level=info msg=“signal received” signal=terminated

Nov 20 00:30:48 ip-172-31-41-91 chirpstack-gateway-bridge[17796]: time=“2020-11-20T00:30:48Z” level=warning msg=“shutting down server”

Nov 20 00:30:48 ip-172-31-41-91 systemd[1]: Stopped ChirpStack Gateway Bridge.

Nov 20 00:30:48 ip-172-31-41-91 systemd[1]: Started ChirpStack Gateway Bridge.

Nov 20 00:30:48 ip-172-31-41-91 chirpstack-gateway-bridge[15781]: time=“2020-11-20T00:30:48Z” level=info msg=“starting ChirpStack Gateway Bridge” docs=“https://www.chirpstack.io/gateway-bridge/” version=3.9.2

Nov 20 00:30:48 ip-172-31-41-91 chirpstack-gateway-bridge[15781]: time=“2020-11-20T00:30:48Z” level=info msg=“backend/semtechudp: starting gateway udp listener” addr=“0.0.0.0:1700”

Nov 20 00:30:48 ip-172-31-41-91 chirpstack-gateway-bridge[15781]: time=“2020-11-20T00:30:48Z” level=info msg=“integration/mqtt: connected to mqtt broker”

My main problem could be I have the wrong config file (.toml), do you think that is the problem?

Notes: I followed the tutorial here

ANY AND ALL HELP IS APPRECIATED

#2

Possible you have the termination on connection error set to true?

  # Terminate on connect error.
  #
  # When set to true, instead of re-trying to connect, the ChirpStack Gateway Bridge
  # process will be terminated on a connection error.
  terminate_on_connect_error=true

Is the mqtt broker on localhost? Odd that it would have an issue connecting if so.

1 Like
#3

Hello John!

I realized that the above are logs thus showing initial errors, now everything seems to be working fine EXCEPT the Gateway is still not connecting to ChirpStack and I am honestly lost.

Issue: My RAK7258 is 'Not Seen by Chirp Stack despite following everything in the tutorial of connecting ChirpStack via AWS Ubuntu
Hello John!
I realized that the above are logs thus showing

image
image1721×587 46.6 KB

ALL tests giving the expected results, namely:

  • journalctl -u chirpstack-network-server -f -n 50
  • journalctl -u chirpstack-application-server -f -n 50
    journalctl -u chirpstack-gateway-bridge -f -n 50

All of them are running as seen below:

image
image2880×512 280 KB

ALL indicate that they are online and running.

Anyone has any clue why this is happening?

My System log seems good

image

Setup: RAK7258

Server: ChipStack Installed on Ubuntu AWS
I haven’t changed my chirpstack- network-server from its default to US915… but would that impact the gateway being found by the chirpstack server hosted on AWS?initial errors, now everything seems to be working fine EXCEPT the Gateway is still not connecting to ChirpStack and I am honestly lost.

Issue: My RAK7258 is 'Not Seen by Chirp Stack despite following everything in the tutorial of connecting ChirpStack via AWS Ubuntu

image
image1721×587 46.6 KB

image
image1721×587 46.6 KB

ALL tests giving the expected results, namely:

  • journalctl -u chirpstack-network-server -f -n 50
  • journalctl -u chirpstack-application-server -f -n 50
    journalctl -u chirpstack-gateway-bridge -f -n 50
    ALL indicate that they are online and running.

As seen below:
For my chirpstack-gateway-bridge :
I restarted it, everything is running

image
image2880×512 280 KB

When I execute: journalctl -u chirpstack-gateway-bridge -f -n 50
I receive errors (logs from when I tried lora-server instead of chirpstack-gateway-bridge)

image
image2880×1472 1.17 MB

But thankfully it is connected to the MQTT.

For Chirpstack-Network-Server:
journalctl -u chirpstack-network-server -f -n 50

image
image2880×914 1.1 MB

image

Which seems weird but when I check status, it is running ->

image
image2880×588 510 KB

For Chirpstack-Application-Server:
It is also running

image
image2880×602 537 KB

And it seems OK as well ->

image
image2880×1430 1.72 MB

Anyone has any clue why this is happening?

My System log seems good

image

Setup: RAK7258

Server: ChipStack Installed on Ubuntu AWS

I haven’t changed my chirpstack- network-server from its default to US915… but would that impact the gateway being found by the chirpstack server hosted on AWS?

#4

Hey Brian. Nothing is standing out to me in the logs you’ve shared.

I did encounter an issue where my gateway’s weren’t being seen because the date/time on them was in the past. Could you check that?

#5

Good Sunday John, yes I checked it :frowning: and it is in sync so that is not the problem.

FOUND THE PROBLEM

Are you ready for this…

I did not set my Semtech Packet Forwarder to UDP but rather I had TCP.
A week and a half later. Whoops.

Ls stand for lessons

1 Like
#6

Ah! Glad you found it. It’s funny how it seems these things are often a “minor” thing overlooked. Again, really glad to hear you found it

1 Like
#7

Hi brian, i dont know if you still remember this but where to change tcp to udp?