Skip to content
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 data is corrupt when the program is started before the connections #229

Open
unknown-spirit opened this issue Jun 17, 2022 · 3 comments

Comments

@unknown-spirit
Copy link
Contributor

I've been using nethogs for years for my BusyTasks app. I recently discovered strange and flawed data and wondered whether it is my program or the nethogs backend. After further investigation I found that nethogs does not output correct data when it's being started before the network connections, it sometimes even crashed. Unfortunately I can't reproduce the crashes, but the data mining problem instead.

Steps for reproduction on Ubuntu 22.04 with recent nethogs version:

  • Disable automatic connecting of all network connections
  • Reboot OS and start "nethogs -Ca"
  • Connect network manually
  • Start another "nethogs -Ca" in a separate window
  • Compare the results

When automatically starting BusyTasks on login, there are two options as workaround:
Either use automatic connecting mode or restart BusyTasks after activating network connections.
I cannot determine if it's a problem with connection handling in the operating system itself. The bug may not occur in older Ubuntu releases.
Thanks for your support

@raboof
Copy link
Owner

raboof commented Jun 19, 2022

With which nethogs versions do you see this problem? 0.8.7, earlier versions as well, test master as well?

@unknown-spirit
Copy link
Contributor Author

I first encountered it with 0.8.6 from the ubuntu repositories. This version even sometimes crashed when connecting/disconnecting, so I downloaded and compiled 0.8.7, which did not crash, but still shows questionable output.
I did not download and install the recent version from github because as far as I see there have not been any relevant commits.

@unknown-spirit unknown-spirit closed this as not planned Won't fix, can't repro, duplicate, stale Jun 19, 2022
@unknown-spirit
Copy link
Contributor Author

Sorry, I misclicked on "close".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants