Issues with new v4 instance

ChirpStack Application Server
1

I’ve configured a new latest v4 docker instance to which I have a gateway with gateway-bridge v4.0.11 . I’m unable to see any live Lorawan frames come in on the gateway but I am seeing that the application is picking them up, in the logs.

chirpstack_1 | 2024-04-26T20:38:30.911144Z INFO chirpstack::gateway::backend::mqtt: Message received from gateway region_id=“eu868” topic=eu868/gateway/1111111111111111/event/up qos=AtMostOnce json=false
chirpstack_1 | 2024-04-26T20:38:30.913999Z ERROR chirpstack::uplink: Deduplication error error=Deduplication put and get lock: Broken pipe (os error 32)
chirpstack_1 | 2024-04-26T20:38:31.080778Z DEBUG gRPC{uri=/api.InternalService/StreamGatewayFrames}: chirpstack::api: Started processing request
chirpstack_1 | 2024-04-26T20:38:31.082405Z INFO gRPC{uri=/api.InternalService/StreamGatewayFrames}: chirpstack::api: Finished processing request status=“200” latency=1.644035ms
chirpstack_1 | 2024-04-26T20:38:31.085229Z ERROR chirpstack::api: Log request error error=Broken pipe (os error 32)
chirpstack_1 | 2024-04-26T20:38:31.085389Z ERROR chirpstack::api::internal: Reading frame-log returned error: XREAD frame stream
chirpstack_1 | 2024-04-26T20:38:31.159403Z DEBUG gRPC{uri=/api.InternalService/StreamGatewayFrames}: chirpstack::api: Started processing request
chirpstack_1 | 2024-04-26T20:38:31.160983Z INFO gRPC{uri=/api.InternalService/StreamGatewayFrames}: chirpstack::api: Finished processing request status=“200” latency=1.634261ms
chirpstack_1 | 2024-04-26T20:38:31.163553Z ERROR chirpstack::api: Log request error error=Broken pipe (os error 32)

2

Those logs mostly show API requests.

The broken pipe is concerning, I would verify your connectivity between services.

3

API is working working just fine:

image
image825×301 63.2 KB

What else could it be?

4

May be you have a proxy in between?
Then you need to proxy the grpc traffic.
You can search for “nginx” in this forum.

5

This issue was resolved. The Redis server was using TLS, but the server was not configured using rediss://.... (note the double ss), because of this ChirpStack could not connect to Redis which caused API calls to fail…