clear donwlink queue

[luis santos]

Hi,

When I try to open the lorawan/donwlink queue page on the gw conduit with AEP 1.4.16.
The lora-network-server process start using 100% of CPU, and reboot +-1 min after.
Is anyone with the same problem?

cumps,

[Jason Reiss]

Has the LoRaWAN > Network Settings > Queue Size setting been changed from the default of 16?

Do these commands produce the same result?
lora-query -x packet queue
lora-query -x packet queue json

[luis santos]

I didn’t change the default value of 16.

The commands don’t produce any result:

admin@AbrantesTorrePT:~# lora-query -x packet queue
admin@AbrantesTorrePT:~# lora-query -x packet queue json

But I have another gw that return results.

https://pastebin.com/1tPX1vEZ

https://pastebin.com/VfjmR8kb

cumps,

• This reply was modified 5 years, 10 months ago by luis santos.
• This reply was modified 5 years, 10 months ago by luis santos.
• This reply was modified 5 years, 10 months ago by luis santos.
• This reply was modified 5 years, 10 months ago by luis santos.

[luis santos]

How can i remove all the queue msg?

[Jason Reiss]

You could try to remove all queued items for each device.
# lora-query -x packet queue delete <DEV-EUI>

[luis santos]

Don’t exist one command that removes the packet queue of all devices?

[Piia]

Hi!

We have also some problems with lora network server queue.
nodeQueueSize is set to 1 in lora-network-server.conf, but it seems that it’s not working properly. If multiple downlinks are sent to device, I can see them all in queue (lora-query -x packet queue). Sometimes we receive queue_full message from network server and we can clear device queue, but not always.

We are using mlinux 3.3.24 & lora network server 2.0.19

• This reply was modified 5 years, 8 months ago by Piia.

[Jason Reiss]

Use deviceQueueSize

[Piia]

Thanks, it works!

[Piia]

Hi!

Still one question related to this queue clearing. I have set deviceQueueSize to 2 in config. When I send some commands to device (more that 2) I receive queue_full message, and our app clears the queue. If I use this command to check situation: lora-query -x packet queue, the queue is empty. If I then try to send again downlink to device, I receive the queue_full message again, even the queue seems to be empty so I can’t send any messages to device. Why?

-Piia

[Piia]

Hi!

Related to previous question, here some more info:

root@mtcdt:# lora-query -x packet queue delete 3741500d00450044
{“data”:null,”status”:”success”}

root@mtcdt:/var/iot-gw-backend-storage# mosquitto_sub -v -t “#”| grep 45-00-44
lora/37-41-50-0d-00-45-00-44/down {“data”:”QQU=”,”ack”:true}
lora/37-41-50-0d-00-45-00-44/down_dropped {“ack”:true,”data”:”QQU=”,”data_size”:4,”deveui”:”3741500d00450044″}
lora/37-41-50-0d-00-45-00-44/queue_full (null)

Why the queue of device 37-41-50-0d-00-45-00-44 is full after clearing?

-Piia

[Jason Reiss]

A bug exists where the memory queue will not be cleared from the lora-query command. Likewise the database queue is not cleared when an MQTT message to clear the queue is issued. The next version, release pending, will have this issue fixed.

MQTT message to lora/EUI/clear and lora-query -x packet queue delete will empty both on the current release.

[Author]

Posts