Solved FlexQoS problems with Merlin 386.1_2

[sbsnb]

I've been using FlexQoS for quite some time without issue, but ever since I updated to Merlin's 386.1_2 this morning my log is filling up with these error messages:

Feb 24 16:07:12 FlexQoS: TC Modification Delay reached maximum 300 seconds
Feb 24 16:07:12 FlexQoS: TC Modification delayed for 300 seconds
Feb 24 16:07:12 FlexQoS: Scheduled Persistence Check -> Reapplying Changes
Feb 24 16:07:13 FlexQoS: Applying AppDB static rules
Feb 24 16:07:13 FlexQoS: RTNETLINK answers: Invalid argument
Feb 24 16:07:13 FlexQoS: We have an error talking to the kernel
Feb 24 16:07:13 FlexQoS: RTNETLINK answers: Invalid argument
Feb 24 16:07:13 FlexQoS: We have an error talking to the kernel
Feb 24 16:07:13 FlexQoS: Adaptive QoS not fully done setting up prior to modification script
Feb 24 16:07:13 FlexQoS: (Skipping class modification, delay trigger time period needs increase)
Feb 24 16:07:13 FlexQoS: Applying AppDB custom rules and TC rates
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:07:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:12:00 FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=2895) called with 1 args: -check
Feb 24 16:12:01 FlexQoS: TC Modification Delayed Start
Feb 24 16:17:12 FlexQoS: TC Modification Delay reached maximum 300 seconds
Feb 24 16:17:12 FlexQoS: TC Modification delayed for 300 seconds
Feb 24 16:17:12 FlexQoS: Scheduled Persistence Check -> Reapplying Changes
Feb 24 16:17:13 FlexQoS: Applying AppDB static rules
Feb 24 16:17:13 FlexQoS: RTNETLINK answers: Invalid argument
Feb 24 16:17:13 FlexQoS: We have an error talking to the kernel
Feb 24 16:17:13 FlexQoS: RTNETLINK answers: Invalid argument
Feb 24 16:17:13 FlexQoS: We have an error talking to the kernel
Feb 24 16:17:13 FlexQoS: Adaptive QoS not fully done setting up prior to modification script
Feb 24 16:17:13 FlexQoS: (Skipping class modification, delay trigger time period needs increase)
Feb 24 16:17:13 FlexQoS: Applying AppDB custom rules and TC rates
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:17:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:22:00 FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=4662) called with 1 args: -check
Feb 24 16:22:01 FlexQoS: TC Modification Delayed Start
Feb 24 16:27:12 FlexQoS: TC Modification Delay reached maximum 300 seconds
Feb 24 16:27:12 FlexQoS: TC Modification delayed for 300 seconds
Feb 24 16:27:12 FlexQoS: Scheduled Persistence Check -> Reapplying Changes
Feb 24 16:27:13 FlexQoS: Applying AppDB static rules
Feb 24 16:27:13 FlexQoS: RTNETLINK answers: Invalid argument
Feb 24 16:27:13 FlexQoS: We have an error talking to the kernel
Feb 24 16:27:13 FlexQoS: RTNETLINK answers: Invalid argument
Feb 24 16:27:13 FlexQoS: We have an error talking to the kernel
Feb 24 16:27:13 FlexQoS: Adaptive QoS not fully done setting up prior to modification script
Feb 24 16:27:13 FlexQoS: (Skipping class modification, delay trigger time period needs increase)
Feb 24 16:27:13 FlexQoS: Applying AppDB custom rules and TC rates
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value
Feb 24 16:27:13 FlexQoS: Error: argument "-1" is wrong: invalid priority value

Not sure how to interpret this.

 

[dave14305]

What version of FlexQoS? There are messages in that log that aren’t part of the current version. Make sure you’re on the latest stable version (1.2.1).

 

[sbsnb]

Let me check. I've never updated manually. I just kind of assumed it would update itself when it ran its cron job.

 

[forkyishere]

That could explain why I went from my usual upload rate (>200Mbps) to a 1Mbps on a specific device... I found that adding a bandwidth limiter with a higher number of bandwidth works as a workaround.

 

[sbsnb]

Update fixed the issue.