Bug #8193
openWorker names cut off when having more than 99 workers and statistics incomplete in the json stats logging
Description
Running version 8.0.1 with 2 interfaces with 120 workers each (af-packet mode).
When enabling per thread statistics logging to both stats.log and eve.1.json (to see if there was any difference between the 2), I observed the following:
1) Looking at stats.log: worker names loose the last character starting at worker number 100 and above:
Up to worker 99, the names are as follows:
W#01-pcap0, W#02-pcap0, ... W#99-pcap0, but starting at 100 it becomes: W#100-pcap, W#101-pcap .. W#120-pcap. The trailing 0 is missing.
Same goes for the second interface: W#01-pcap1, W#02-pcap1 ... W#99-pcap1 and then it becomes W#100-pcap and so on.
2) While the stats.log is complete, that is: it contains statistics for all 240 workers (although the names are not complete as explained above), the eve.1.json is not.
It does report all 120 worker stats for the first interface but stops at worker 99 for the second interface.
Probably due to a duplicate key in the json (as both W#100-pcap0 and W#100-pcap1 are transformed into W#100-pcap), the counters for W#100-pcap and above in the eve log match those of the second interface when compared to the counters in the stats.log output.
I tried shortening the names of the interfaces to even less characters by simply renaming them to p1 and p2, but that doesn't make any difference. Even in that case, the last character is removed starting at worker 100.
Let me know if you want me to run any specific tests.
Thanks, John
No data to display