Help understanding why, "get device-sessions for dev_addr error: object does not exist" is being generated

ChirpStack Network Server
1

I’ve deleted a dead device from our network, but i’m still seeing the following WARN messages in the Chirpstack Network server logs.

Jun 30 19:51:41 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:41Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=f105d2ea-540f-47e1-8f1d-2f1b7cefe17d dev_addr=eeecdf85 dev_eui=00007cf2dd211fdd

Jun 30 19:51:41 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:41Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=9fd6305f-f151-4a38-bc05-62ddadbc00cd dev_addr=eeed9951 dev_eui=00007cf2dd211fdd

Jun 30 19:51:43 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:43Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=d40850ac-4c4a-4cc1-9ecc-c6cbe749b4aa dev_addr=eeec3c66 dev_eui=00007cf2dd211fdd

Jun 30 19:51:45 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:45Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=aee50bcf-ba85-4768-8a1b-d6be3dca8eb2 dev_addr=eeec2618 dev_eui=00007cf2dd211fdd

Jun 30 19:51:47 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:47Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=c5dbf499-e65b-44ce-9b22-6addb08cfca5 dev_addr=eeed061c dev_eui=00007cf2dd211fdd

Jun 30 19:51:48 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:48Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=c426673b-d846-463a-ae21-f68b3ff9ad1c dev_addr=eeedd076 dev_eui=00007cf2dd211fdd

Jun 30 19:51:49 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:49Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=f1f61dd3-a612-4a93-a0c2-74d35e185ec0 dev_addr=eeed986f dev_eui=00007cf2dd211fdd

Jun 30 19:51:49 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:49Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=84e54323-7acf-4623-817c-cfd6cc67c5df dev_addr=eeec5e00 dev_eui=00007cf2dd211fdd

Jun 30 19:51:53 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:53Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=6e84007f-ca36-4b44-83e9-bba63f8023ca dev_addr=eeec2618 dev_eui=00007cf2dd211fdd

Jun 30 19:51:55 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:55Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=9973bdf8-3ce6-4516-b928-76c7b5ad3fe0 dev_addr=eeed061c dev_eui=00007cf2dd211fdd

Jun 30 19:51:56 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:56Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=7fd29f12-8d74-42c1-82a3-39b6afef7948 dev_addr=eeece6b1 dev_eui=00007cf2dd211fdd

Jun 30 19:51:56 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:56Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=fd70c6d8-dfd0-4fe2-ba78-e298a4b0a3b4 dev_addr=eeecf845 dev_eui=00007cf2dd211fdd

Jun 30 19:51:57 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:57Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=aa60e685-35ea-4b7b-ab1a-b7166cc07cbb dev_addr=eeec1835 dev_eui=00007cf2dd211fdd

Jun 30 19:51:59 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:59Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=fbd2f047-75de-49be-ae04-683578f53da0 dev_addr=eeec71d0 dev_eui=00007cf2dd211fdd

Jun 30 19:51:59 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:51:59Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=d6dc3500-36a5-4811-924d-33be449f04d6 dev_addr=eeedbafe dev_eui=00007cf2dd211fdd

Jun 30 19:52:00 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:52:00Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=b9e52548-f93d-4dcd-8670-412f95973510 dev_addr=eeed1b10 dev_eui=00007cf2dd211fdd

Jun 30 19:52:03 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:52:03Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=40736f92-66af-492d-ba0d-89c290c0df21 dev_addr=eeed1bf6 dev_eui=00007cf2dd211fdd

Jun 30 19:52:04 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:52:04Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=0df93a22-5a58-4438-b34e-e3f30141a1fb dev_addr=eeed061c dev_eui=00007cf2dd211fdd

Jun 30 19:52:06 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:52:06Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=31a5c99c-e17a-4564-861c-e308c8dfc811 dev_addr=eeed150f dev_eui=00007cf2dd211fdd

Jun 30 19:52:09 ip-10-36-10-138 chirpstack-network-server[77467]: time=“2025-06-30T19:52:09Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=989407c3-7dac-4a83-bbd6-6bec859d1d74 dev_addr=eeec3893 dev_eui=00007cf2dd211fdd

Would someone be able to tell why the Chirpstack Network Server is generating these logs after deleting the device? How can I prevent this from continuing?

2

Here’s an actual better representation of the issue triggered by an uplink message>

time=“2025-07-02T23:56:11Z” level=info msg=“uplink: frame(s) collected” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 mtype=UnconfirmedDataUp uplink_ids=“[cbe83ded-fdbb-4055-b5a9-98c22dee605d]”

time=“2025-07-02T23:56:11Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_addr=eeed81b9 dev_eui=00007cf2dd215123

time=“2025-07-02T23:56:11Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_addr=eeed81b9 dev_eui=00007cf2dd2099f5

time=“2025-07-02T23:56:11Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_addr=eeed81b9 dev_eui=00007cf2dd2075d9

time=“2025-07-02T23:56:11Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_addr=eeed81b9 dev_eui=00007cf2dd20af88

time=“2025-07-02T23:56:11Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_addr=eeed81b9 dev_eui=00007cf2dd210de0

time=“2025-07-02T23:56:11Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_addr=eeed81b9 dev_eui=00007cf2dd209747

time=“2025-07-02T23:56:11Z” level=warning msg=“get device-sessions for dev_addr error: object does not exist” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_addr=eeed81b9 dev_eui=00007cf2dd202ff4

time=“2025-07-02T23:56:11Z” level=debug msg=“skipping geolocation, it is disabled by the service-profile” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_eui=00007cf2dd20fcf9

time=“2025-07-02T23:56:11Z” level=info msg=“sent uplink meta-data to network-controller” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_eui=00007cf2dd20fcf9

time=“2025-07-02T23:56:11Z” level=info msg=“device gateway rx-info meta-data saved” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_eui=00007cf2dd20fcf9

time=“2025-07-02T23:56:11Z” level=info msg=“device-session saved” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_addr=eeed81b9 dev_eui=00007cf2dd20fcf9

time=“2025-07-02T23:56:11Z” level=info msg=“finished client unary call” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 grpc.code=OK grpc.ctx_id=3c521e0c-7af7-461a-8f7e-52eadf089032 grpc.duration=5.872374ms grpc.method=HandleUplinkData grpc.service=as.ApplicationServerService span.kind=client system=grpc

time=“2025-07-02T23:56:12Z” level=info msg=“pending mac-command block set” cid=LinkADRReq commands=2 ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_eui=00007cf2dd20fcf9

time=“2025-07-02T23:56:12Z” level=info msg=“gateway/mqtt: publishing gateway command” command=down downlink_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 gateway_id=647fdafffe01174c qos=0 topic=gateway/647fdafffe01174c/command/down

time=“2025-07-02T23:56:12Z” level=info msg=“device-session saved” ctx_id=f805239a-6c81-4e4e-8cbe-42bf51c15852 dev_addr=eeed81b9 dev_eui=00007cf2dd20fcf9

Why is the network server pulling device sessions for so many devices for one uplink message? How can I prevent this from happening?

3

I saw these warning some time too.
But see no impact so I ignore it.

May be you can download the source code and do a “search” on these errors to know the reason.