What's new

QoS setup rule fail error in logs since updating to 384.9

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

ZenitH-AT

Occasional Visitor
I've been getting the following messages in logs since updating my firmware:

Code:
Feb 13 03:54:51 rc_service: httpd 253:notify_rc restart_qos;restart_firewall
Feb 13 03:55:13 BWDPI: fun bitmap = 83
Feb 13 03:55:13 A.QoS: qos_count=0, qos_check=1
Feb 13 03:55:16 A.QoS: qos rule is less than 22
Feb 13 03:55:16 A.QoS: restart A.QoS because set_qos_conf / set_qos_on / setup rule fail
Feb 13 03:55:17 A.QoS: qos_count=0, qos_check=1
Feb 13 03:55:21 A.QoS: qos rule is less than 22
Feb 13 03:55:21 A.QoS: restart A.QoS because set_qos_conf / set_qos_on / setup rule fail
Feb 13 03:55:22 A.QoS: qos_count=1, qos_check=1
Feb 13 03:55:25 A.QoS: qos rule is less than 22
Feb 13 03:55:25 A.QoS: restart A.QoS because set_qos_conf / set_qos_on / setup rule fail
Feb 13 03:55:26 A.QoS: qos_count=2, qos_check=1
Feb 13 03:55:26 A.QoS: qos rule is less than 22
Feb 13 03:55:26 A.QoS: restart A.QoS because set_qos_conf / set_qos_on / setup rule fail
Feb 13 03:55:26 miniupnpd[4338]: shutting down MiniUPnPd
Feb 13 03:55:27 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Feb 13 03:55:27 miniupnpd[10941]: HTTP listening on port 33721
Feb 13 03:55:27 miniupnpd[10941]: Listening for NAT-PMP/PCP traffic on port 5351

I noticed some simmilar posts in a FreshJR thread but I'm not using any QoS scripts.

I'm using Adaptive QoS with fq_codel and I've tried lowering the download and upload bandwidth a bit but it hasn't changed the errors.
 
I've been getting the following messages in logs since updating my firmware:

Code:
Feb 13 03:54:51 rc_service: httpd 253:notify_rc restart_qos;restart_firewall
Feb 13 03:55:13 BWDPI: fun bitmap = 83
Feb 13 03:55:13 A.QoS: qos_count=0, qos_check=1
Feb 13 03:55:16 A.QoS: qos rule is less than 22
Feb 13 03:55:16 A.QoS: restart A.QoS because set_qos_conf / set_qos_on / setup rule fail
Feb 13 03:55:17 A.QoS: qos_count=0, qos_check=1
Feb 13 03:55:21 A.QoS: qos rule is less than 22
Feb 13 03:55:21 A.QoS: restart A.QoS because set_qos_conf / set_qos_on / setup rule fail
Feb 13 03:55:22 A.QoS: qos_count=1, qos_check=1
Feb 13 03:55:25 A.QoS: qos rule is less than 22
Feb 13 03:55:25 A.QoS: restart A.QoS because set_qos_conf / set_qos_on / setup rule fail
Feb 13 03:55:26 A.QoS: qos_count=2, qos_check=1
Feb 13 03:55:26 A.QoS: qos rule is less than 22
Feb 13 03:55:26 A.QoS: restart A.QoS because set_qos_conf / set_qos_on / setup rule fail
Feb 13 03:55:26 miniupnpd[4338]: shutting down MiniUPnPd
Feb 13 03:55:27 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Feb 13 03:55:27 miniupnpd[10941]: HTTP listening on port 33721
Feb 13 03:55:27 miniupnpd[10941]: Listening for NAT-PMP/PCP traffic on port 5351

I noticed some simmilar posts in a FreshJR thread but I'm not using any QoS scripts.

I'm using Adaptive QoS with fq_codel and I've tried lowering the download and upload bandwidth a bit but it hasn't changed the errors.
Ignore this. It's debug info for Asus. This is normal for all of us.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top