Page 1 of 1
Max Queue Errors
Posted: Thu May 15, 2025 5:07 pm
by Steve G
May 15 09:07:29 bwmgr kernel: Queue Full: len:3000 max:3000
We're getting these messages in our log. What does it mean and how can we fix it?
Re: Max Queue Errors
Posted: Thu May 15, 2025 6:36 pm
by Bob
Steve G wrote: Thu May 15, 2025 5:07 pm
May 15 09:07:29 bwmgr kernel: Queue Full: len:3000 max:3000
We're getting these messages in our log. What does it mean and how can we fix it?
You need to increase your max_qlen setting:
sysctl -a | grep max_qlen
The default is 3000. This is set when you create the rule, so you need to set this in your bootup sysctl config:
edit /etc/sysctl.conf:
And then reboot. If you’re just having a problem with 1 rule you could just do
sysctl bwmgr.max_qlen=5000
and then re-create the rule
Re: Max Queue Errors
Posted: Thu May 15, 2025 8:17 pm
by Dennis
Note that this will be dynamic shortly. The queue depth should be calculated based on the allowed bandwidth. In fact I’m going to add that as a priority task.
TCP traffic gets window shaped so if you’re blowing. your queue it means you have a lot of icmp or udp traffic and you might want to see what they’re doing if this is an individual customer rule.
Re: Max Queue Errors
Posted: Thu May 22, 2025 3:45 pm
by Bob
As of 8.071 you can override the default max queue length (ie the number of packets that can be delayed) in both profiles and individual rules
Re: Max Queue Errors
Posted: Fri May 23, 2025 12:23 pm
by Dennis
The max_qlen setting for each rule is now dynamic based on the bandwidth setting for the rule. It will not exceed the sysctl setting for bwmgr.max_qlen. You can override this in profiles or individual rules