-
-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nethogs keeps counting network usage for a process that long terminated #277
Comments
|
hello raboof, your reading of the issue is not correct. What is completely wrong and indeed scary when nethogs KEEPS ON COUNTING TRAFFIC UP FOR A PROCESS THAT LONG TERMINATED. And i do not refer to the "TOTAL" in above picture. How can a non existing process consume network traffic? The process 8340 terminated at about Sent 1821.599 (or so) and kept on counting for hours way beyond the 2000.000 mark. This to me is scary. zombie traffic? Sadly Nethogs entirely cannot be taken serious. |
Ah, that is surprising indeed, thanks for clarifying. I suspect it's mis-attributing traffic that was used by 8374 to 8340, possibly because it was using the same ip+port pairs. Looks like we should be more aggressively clearing the mapping cache from ip+port pairs to processes. Does that sound like it'd match what you saw? |
(I'm not enjoying the all-caps and "cannot be taken serious" hyperbole btw - remember there's a human on the other end) |
i cannot verify if this is a mapping issue, all i can spot is that traffic is being recorded for a long terminated process. whether this is false attributing, or double counting, or even wrong counting is not visible to me. |
scary!
nethogs keeps counting network usage for processes that long terminated!
command: sudo nethogs -P 8374 -P 8340 -v 3
process 8340 terminated 7 minutes ago, but nethogs keeps on counting data for that process.
The text was updated successfully, but these errors were encountered: