finyyu
July 21, 2021, 11:44am
1
This is my first time to install chirpstack on Raspberry PI 4, and device cannot join success. then install the the same version chirpstack on other server(x86) with Respberry Pi, device join success.
This problem has confused me for several days, I don’t know if anyone has encountered this problem, if there is a solution, I would be very grateful
OS information as below:#1414 SMP Fri Apr 30 13:20:47 BST 2021 armv7l GNU/Linux
Raspberry Pi version:
Operation:
Add network-servers, gateway-profiles, service-profiles and device-profiles(supports OTAA)
Add gateway, application and device, set [KEYS(OTAA)]
Using device to join, there is only [JoinRequest], but not response of [JoinAccept].
Network server logs likes:
1 Like
Which versions do you have installed?
finyyu
July 23, 2021, 2:06am
3
Application Server 3.15.0
And which ChirpStack Gateway Bridge version?
Dan
September 6, 2021, 3:02am
6
Same issue on RPi compute 3+
Sep 06 12:59:47 raspberrypi docker-compose[831]: chirpstack-gateway-bridge_1 | time="2021-09-06T02:59:47.628962589Z" level=info msg="integration/mqtt: publishing event" event=up qos=0 topic=gateway/b827ebfffee35c08/event/up uplink_id=a6637752-d553-4d6c-b6c7-f2546995db78
Sep 06 12:59:47 raspberrypi docker-compose[831]: chirpstack-network-server_1 | time="2021-09-06T02:59:47.632179796Z" level=info msg="gateway/mqtt: uplink frame received" gateway_id=b827ebfffee35c08 uplink_id=a6637752-d553-4d6c-b6c7-f2546995db78
Sep 06 12:59:47 raspberrypi docker-compose[831]: chirpstack-network-server_1 | time="2021-09-06T02:59:47.842023338Z" level=error msg="uplink: processing uplink frame error" ctx_id=dfec6344-8d23-46d2-9d7b-1723cb1f5d1a error="zero items in collect set"
network-server config:
[postgresql]
dsn="postgres://chirpstack_ns:chirpstack_ns@postgresql/chirpstack_ns?sslmode=disable"
[redis]
url="redis://redis:6379"
[network_server]
net_id="000000"
device_session_ttl="876000h0m0s"
[network_server.band]
name="AU_915_928"
[network_server.network_settings]
enabled_uplink_channels=[]
[network_server.gateway.backend.mqtt]
server="tcp://mosquitto:1883"
username=""
password=""
[join_server.default]
server="http://chirpstack-application-server:8003"
Hi @Dan
Increase deduplication_delay settings in the chirpstack-network-server configuration file and restart the network server and try again.
# Time to wait for uplink de-duplication.
#
# This is the time that ChirpStack Network Server will wait for other gateways to receive
# the same uplink frame. Valid units are 'ms' or 's'.
# Please note that this value has an influence on the uplink/downlink
# roundtrip time. Setting this value too high means ChirpStack Network Server will be
# unable to respond to the device within its receive window.
deduplication_delay="200ms"
Dan
September 6, 2021, 3:57am
8
No differentlocalhost) and there is only 1
Hi @sagarpatel deduplication_delay in the chirpstack-network-server.toml:
[postgresql]
dsn="postgres://chirpstack_ns:chirpstack_ns@postgresql/chirpstack_ns?sslmode=disable"
[redis]
url="redis://redis:6379"
[network_server]
net_id="000000"
[network_server.band]
name="EU868"
[network_server.gateway.backend.mqtt]
server="tcp://wazigate-edge:1883"
client_id="chirpstack-network-server"
[join_server.default]
server="http://chirpstack-application-server:8003"
In any case, in which section of the file should I add it?
OK I found it, it’s in [network_server] according to doc.
So, I tried adding deduplication_delay="400ms", but no luck.redis-cli --scan, it’s empty.
1 Like
I tried the redis monitor:
$ redis-cli monitor
-1097016368.000000 [0 172.18.0.7:55036] "multi"
-1097016536.000000 [0 172.18.0.7:55036] "sadd" "lora:ns:rx:collect:08a0cff89d031a09087d100c1a03342f35:40221d0126001c00015096c955d4c1be31" "\n\x11@\"\x1d\x01&\x00\x1c\x00\x01P\x96\xc9U\xd4\xc1\xbe1\x12\x11\b\xa0\xcf\xf8\x9d\x03\x1a\t\b}\x10\x0c\x1a\x034/5\x1a:\n\b\xaaU\xa0\x00\x00\x00\x00\x00(\xb1\xff\xff\xff\xff\xff\xff\xff\xff\x011\x00\x00\x00\x00\x00\x00\x1c@z\x04\x1b=\xbc\x1f\x82\x01\x10\x85\xdc_Z\x1c\xc8E\xf4\x92Xjh\xa71k\x8b\x88\x01\x02"
-1097016536.000000 [0 172.18.0.7:55036] "pexpire" "lora:ns:rx:collect:08a0cff89d031a09087d100c1a03342f35:40221d0126001c00015096c955d4c1be31" "20000"
-1097016432.000000 [0 172.18.0.7:55036] "exec"
-1097016368.000000 [0 172.18.0.7:55036] "set" "lora:ns:rx:collect:08a0cff89d031a09087d100c1a03342f35:40221d0126001c00015096c955d4c1be31:lock" "lock" "ex" "20" "nx"
-1097016368.000000 [0 172.18.0.7:55036] "smembers" "lora:ns:rx:collect:08a0cff89d031a09087d100c1a03342f35:40221d0126001c00015096c955d4c1be31"
-1097016368.000000 [0 172.18.0.7:55036] "del" "lora:ns:rx:collect:08a0cff89d031a09087d100c1a03342f35:40221d0126001c00015096c955d4c1be31"
Do you see anything wrong?smembers command myself, before the del:
$ redis-cli "smembers" "lora:ns:rx:collect:08a0cff89d031a09087d100c1a03342f35:40221d0126001100019812a16535d60590"
(empty list or set)
1 Like
Dan
September 7, 2021, 12:16am
12
my full server logs including redis logs:
Sep 07 10:08:36 raspberrypi docker-compose[3997]: chirpstack-gateway-bridge_1 | time="2021-09-07T00:08:36.324967623Z" level=info msg="integration/mqtt: publishing event" event=up qos=0 topic=gateway/b827ebfffee35c08/event/up uplink_id=9baf35de-f766-4282-8668-d99b2751a12b
Sep 07 10:08:36 raspberrypi docker-compose[3997]: chirpstack-network-server_1 | time="2021-09-07T00:08:36.32696214Z" level=info msg="gateway/mqtt: uplink frame received" gateway_id=b827ebfffee35c08 uplink_id=9baf35de-f766-4282-8668-d99b2751a12b
Sep 07 10:08:36 raspberrypi docker-compose[3997]: redis_1 | 1:M 26 Apr 2037 09:30:24.000 * Background saving terminated with success
Sep 07 10:08:36 raspberrypi docker-compose[3997]: redis_1 | 1:M 26 Apr 2037 09:35:12.000 * 1 changes in 3600 seconds. Saving...
Sep 07 10:08:36 raspberrypi docker-compose[3997]: redis_1 | 1:M 26 Apr 2037 09:34:32.000 * Background saving started by pid 8858
Sep 07 10:08:36 raspberrypi docker-compose[3997]: chirpstack-network-server_1 | time="2021-09-07T00:08:36.836852523Z" level=error msg="uplink: processing uplink frame error" ctx_id=d2e829cb-dd49-46fb-a0c1-bf54f59f0a6f error="zero items in collect set"
Sep 07 10:08:36 raspberrypi docker-compose[3997]: redis_1 | 8858:C 26 Apr 2037 08:19:44.000 * DB saved on disk
Sep 07 10:08:36 raspberrypi docker-compose[3997]: redis_1 | 8858:C 26 Apr 2037 09:34:32.000 * RDB: 0 MB of memory used by copy-on-write
Sep 07 10:08:40 raspberrypi docker-compose[3997]: chirpstack-gateway-bridge_1 | time="2021-09-07T00:08:40.708314029Z" level=info msg="integration/mqtt: publishing event" event=stats qos=0 stats_id=8a84fd54-6837-4d22-b172-269304e1a2c8 topic=gateway/b827ebfffee35c08/event/stats
Sep 07 10:08:40 raspberrypi docker-compose[3997]: chirpstack-network-server_1 | time="2021-09-07T00:08:40.712909152Z" level=info msg="gateway/mqtt: gateway stats packet received" gateway_id=b827ebfffee35c08 stats_id=8a84fd54-6837-4d22-b172-269304e1a2c8
Sep 07 10:08:40 raspberrypi docker-compose[3997]: redis_1 | 1:M 26 Apr 2037 09:30:24.000 * Background saving terminated with success
Sep 07 10:08:40 raspberrypi docker-compose[3997]: chirpstack-network-server_1 | time="2021-09-07T00:08:40.720104099Z" level=info msg="storage: gateway state updated" ctx_id=8a84fd54-6837-4d22-b172-269304e1a2c8 gateway_id=b827ebfffee35c08
Sep 07 10:08:40 raspberrypi docker-compose[3997]: chirpstack-application-server_1 | time="2021-09-07T00:08:40.736358668Z" level=info msg="gateway updated" ctx_id=51d1fcc0-846d-41bb-8f9f-6566e8e2bb02 id=b827ebfffee35c08 name=default-gateway
Sep 07 10:08:40 raspberrypi docker-compose[3997]: chirpstack-application-server_1 | time="2021-09-07T00:08:40.749227584Z" level=info msg="metrics saved" aggregation="[MINUTE HOUR DAY MONTH]" ctx_id=51d1fcc0-846d-41bb-8f9f-6566e8e2bb02 name="gw:b827ebfffee35c08"
Sep 07 10:08:40 raspberrypi docker-compose[3997]: chirpstack-application-server_1 | time="2021-09-07T00:08:40.749525446Z" level=info msg="finished unary call with code OK" ctx_id=51d1fcc0-846d-41bb-8f9f-6566e8e2bb02 grpc.code=OK grpc.method=HandleGatewayStats grpc.service=as.ApplicationServerService grpc.start_time="2021-09-07T00:08:40Z" grpc.time_ms=22.819 peer.address="172.18.0.2:47088" span.kind=server system=grpc
Sep 07 10:08:40 raspberrypi docker-compose[3997]: chirpstack-network-server_1 | time="2021-09-07T00:08:40.750906634Z" level=info msg="finished client unary call" ctx_id=8a84fd54-6837-4d22-b172-269304e1a2c8 grpc.code=OK grpc.ctx_id=51d1fcc0-846d-41bb-8f9f-6566e8e2bb02 grpc.duration=25.533563ms grpc.method=HandleGatewayStats grpc.service=as.ApplicationServerService span.kind=client system=grpc
Sep 07 10:08:45 raspberrypi docker-compose[3997]: chirpstack-gateway-bridge_1 | time="2021-09-07T00:08:45.087778898Z" level=info msg="integration/mqtt: publishing event" event=up qos=0 topic=gateway/b827ebfffee35c08/event/up uplink_id=aa58d45e-37fc-4396-8114-a9860d2e0442
Sep 07 10:08:45 raspberrypi docker-compose[3997]: chirpstack-network-server_1 | time="2021-09-07T00:08:45.090849605Z" level=info msg="gateway/mqtt: uplink frame received" gateway_id=b827ebfffee35c08 uplink_id=aa58d45e-37fc-4396-8114-a9860d2e0442
Sep 07 10:08:45 raspberrypi docker-compose[3997]: redis_1 | 1:M 26 Apr 2037 09:35:12.000 * 1 changes in 3600 seconds. Saving...
Sep 07 10:08:45 raspberrypi docker-compose[3997]: redis_1 | 1:M 26 Apr 2037 09:34:32.000 * Background saving started by pid 8859
Sep 07 10:08:45 raspberrypi docker-compose[3997]: redis_1 | 8859:C 26 Apr 2037 08:19:44.000 * DB saved on disk
Sep 07 10:08:45 raspberrypi docker-compose[3997]: redis_1 | 8859:C 26 Apr 2037 09:34:32.000 * RDB: 0 MB of memory used by copy-on-write
Sep 07 10:08:45 raspberrypi docker-compose[3997]: redis_1 | 1:M 26 Apr 2037 09:30:24.000 * Background saving terminated with success
Sep 07 10:08:45 raspberrypi docker-compose[3997]: chirpstack-network-server_1 | time="2021-09-07T00:08:45.601499773Z" level=error msg="uplink: processing uplink frame error" ctx_id=fcf409f7-e62b-45f9-beac-266f490e6852 error="zero items in collect set"
Sep 07 10:08:51 raspberrypi docker-compose[3997]: chirpstack-gateway-bridge_1 | time="2021-09-07T00:08:51.120851502Z" level=info msg="integration/mqtt: publishing event" event=up qos=0 topic=gateway/b827ebfffee35c08/event/up uplink_id=6fb94088-41c8-4772-b209-9d7f887e614c
Sep 07 10:08:51 raspberrypi docker-compose[3997]: chirpstack-network-server_1 | time="2021-09-07T00:08:51.123273985Z" level=info msg="gateway/mqtt: uplink frame received" gateway_id=b827ebfffee35c08 uplink_id=6fb94088-41c8-4772-b209-9d7f887e614c
Sep 07 10:08:51 raspberrypi docker-compose[3997]: redis_1 | 1:M 26 Apr 2037 09:35:12.000 * 1 changes in 3600 seconds. Saving...
Sep 07 10:08:51 raspberrypi docker-compose[3997]: redis_1 | 1:M 26 Apr 2037 09:34:32.000 * Background saving started by pid 8860
Sep 07 10:08:51 raspberrypi docker-compose[3997]: redis_1 | 8860:C 26 Apr 2037 08:19:44.000 * DB saved on disk
Sep 07 10:08:51 raspberrypi docker-compose[3997]: redis_1 | 8860:C 26 Apr 2037 09:34:32.000 * RDB: 0 MB of memory used by copy-on-write
Sep 07 10:08:51 raspberrypi docker-compose[3997]: redis_1 | 1:M 26 Apr 2037 09:30:24.000 * Background saving terminated with success
Sep 07 10:08:51 raspberrypi docker-compose[3997]: chirpstack-network-server_1 | time="2021-09-07T00:08:51.632030729Z" level=error msg="uplink: processing uplink frame error" ctx_id=1353ac17-8bce-4283-878b-e641187de218 error="zero items in collect set"
Dan
September 29, 2021, 2:19am
13
can confirm it was purely to do with redis or postgres. switched back to older versions of both and works normal as expected