QOS Status output seems to be truncated

Hi,

English is not my mother tongue, sorry for any mistakes I would make.

I’m using IPFire 2.25 (x86_64) - Core Update 158.
QOS is enabled and the config has been generated by the template machanism.
All looks good, but if I click on “Status”, it seems the output is truncated.

However, if I connect through SSH to my IPFire machine and I enter “qosctrl status” as root, the command completes successfully, displaying many lines of output.

qosctrl status
[qdisc]
qdisc htb 1: root refcnt 9 r2q 10 default 0x110 direct_packets_stat 0 direct_qlen 1000
Sent 1014379 bytes 4835 pkt (dropped 0, overlimits 235 requeues 4)
backlog 0b 0p requeues 4
qdisc fq_codel 120: parent 1:120 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
Sent 7729 bytes 71 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
maxpacket 153 drop_overlimit 0 new_flow_count 71 ecn_mark 0
new_flows_len 1 old_flows_len 0
qdisc fq_codel 102: parent 1:102 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
Sent 13749 bytes 151 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
maxpacket 113 drop_overlimit 0 new_flow_count 151 ecn_mark 0
new_flows_len 1 old_flows_len 0
qdisc fq_codel 104: parent 1:104 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
Sent 441622 bytes 704 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
maxpacket 2892 drop_overlimit 0 new_flow_count 230 ecn_mark 0
new_flows_len 1 old_flows_len 2
qdisc fq_codel 110: parent 1:110 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64
Sent 346180 bytes 1010 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0

[…etc…output truncated…]

This makes me think this is just a diplay issue in the web GUI.

I was lucky to have access to 2 other IPFire boxes belonging to a friend.
One is still in Core 157, and does not have the issue.
The other one is in Core 158 (like mine) and has exaclty the same issue.

Could it be a Core 158 bug ?
It’s probably not very bad, because I think it is only cosmetic.

Best Regards.

Yes, this is a newly introduced regression.

@stevee could you please have a look at this?

1 Like

I see the same issue as @zaxxon.

@ms - Should this be entered into Bugzilla?

Yes please. Could you assign it to @stevee straight away?

Done!

https://bugzilla.ipfire.org/show_bug.cgi?id=12666

@zaxxon - thank you for reporting this bug!
:grinning:

1 Like

Hello thanks for reporting this issue.

I’ve sent a patch to our development mailing list which fixes this issue.

https://patchwork.ipfire.org/project/ipfire/patch/20210730175701.2930-1-stefan.schantl@ipfire.org/

-Stefan

4 Likes

Hi,

You’re welcome.

I’m glad I could help.

Thanks to all the team for your good work.

Cheers.

1 Like

Hi,

I upgraded to Core Update 159.
I changed the line “nr 543” in “qos.cgi” like it was done in the patch for bug “12666”.

I can confirm the patched version works properly and displays the full status.

Tanks and Best Regards.

3 Likes