| Summary: | QoS graphs will not updated anymore after update to core174 | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Arne.F <arne.fitzenreiter> |
| Component: | --- | Assignee: | Peter Müller <peter.mueller> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | Balancing | ||
| Priority: | Will affect an average number of users | CC: | adolf.belka, michael.tremer, peter.mueller |
| Version: | 2 | ||
| Hardware: | unspecified | ||
| OS: | Unspecified | ||
|
Description
Arne.F
2023-03-30 18:29:10 UTC
I can reproduce this behaviour. Unfortunately, I need help for this bug, since I could not figure out where collectd will get the information on traffic for different QoS classes from. Any hints are highly appreciated. :-) collectd is not involved at all. tc triggers some functions that parse the data and update the rrd itself. https://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=config/qos;hb=98d78fa824fd30a9bc2b90f7d3831ff20c9997b4 Thanks. Using /sbin/tc from Core Update 173 causes everything to be fine again, so this limits the area where to look for. I would consider this an unintentional change and therefore suggest to change the regular expression that it is going to be happy with either string. Roger that, will do so. https://patchwork.ipfire.org/project/ipfire/patch/20230622155115.1741-1-michael.tremer@ipfire.org/ Given that this has been resolved upstream meanwhile, the regular expression change has become redundant. Fix of reverting the regex change has been tested out in Bug#13150 and verified. Therefore also making this bug as verified. Core Update 176 released https://blog.ipfire.org/post/ipfire-2-27-core-update-176-released |