qos QOS Errors in Log

[saeris]

Hey hey, i noticed that my logfiles are spilling over with QOS errors:

 

[DumaOS] QoS application exception: ERROR: Rule not found in chain stack traceback: ^I?: in function '__new__' ^I?: in functio, '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in function <?:237> ^I(tail call): ? ^I(tail call): ? ^I?: in function '?' ^I?: in function 'reset_interface' ^I?: in function <?:204> ^I?: in function 'try' ^I... ^I[C]: in function 'run' ^I?: in function <?:345> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ? Tuesday, December 31, 2019 08:50:50
[DumaOS] Long call 'del_rule' exception 'ERROR: Rule not found in chain stack traceback: ^I?: in function '__new__' ^I?: in fun,tion '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in main chunk ^I[C]: in function 'require' ^I?: in main chunk ^I[C]: in function 'require' ^I?: in main chunk ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ?' Tuesday, December 31, 2019 08:50:50
[DumaOS] Long call 'del_rule' exception 'ERROR: Rule not found in chain stack traceback: ^I?: in function '__new__' ^I?: in fun,tion '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in main chunk ^I[C]: in function 'require' ^I?: in main chunk ^I[C]: in function 'require' ^I?: in main chunk ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ?' Tuesday, December 31, 2019 08:50:50
[DumaOS] applying qos for zone wan, Tuesday, December 31, 2019 08:50:50

 

And I occasionally get "RPC error 'ERROR_NOENT': Rule not found in chain" when I try to update my QOS settings. Is this expected behaviour due to a mistake on my side?

[Netduma Admin]

Hmm, that's an odd one. Simplest thing to do here is to downgrade back to this firmware: https://kb.netgear.com/000060127/XR500-Firmware-Version-2-3-2-32

Then upgrade back again: https://kb.netgear.com/000061157/XR500-Firmware-Version-2-3-2-56

Hopefully that fixes the issue. If not, could you factory reset the router (as a last resort) as that should then solve the problem. https://kb.netgear.com/000053098/How-do-I-perform-a-factory-reset-on-my-Nighthawk-Pro-Gaming-router

Let us know how you get on.

[saeris]

 

On 1/1/2020 at 9:40 PM, Netduma Admin said:

Hmm, that's an odd one. Simplest thing to do here is to downgrade back to this firmware: https://kb.netgear.com/000060127/XR500-Firmware-Version-2-3-2-32

Then upgrade back again: https://kb.netgear.com/000061157/XR500-Firmware-Version-2-3-2-56

Hopefully that fixes the issue. If not, could you factory reset the router (as a last resort) as that should then solve the problem. https://kb.netgear.com/000053098/How-do-I-perform-a-factory-reset-on-my-Nighthawk-Pro-Gaming-router

Let us know how you get on.

Thanks, I'll try this in the coming days. BUT i need to note that I did the downgrade > upgrade path already after the recent issue that was mentioned here: 

 (I was affected and did the downgrade)

 

[Netduma Fraser]

Okay that's fine, it's likely that a factory reset will fix this so try that first.