-
Notifications
You must be signed in to change notification settings - Fork 24
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
False call for need to restart NetworkManager on RHEL8 #211
Comments
@FrostyX , do you have noticed this issue yet? |
Hello @thomas-merz,
You can try to debug like this: Print more information about NetworkManager:
You can see that, on my computer, Tracer thinks it was affected by the
Then you can verify whether the information is correct or there is a bug somewhere. |
Hi @FrostyX , I did what you suggest and I got this:
These files are much older than
Plus:
|
NetworkManager has been updated 2024-07-07T09:02
And host has been rebooted after update:
|
On some of my RHEL8 VMs
tracer -ea
says that I should restart NetworkManager:I really can't find any reason for this (no updates at all), so is this a false call or how can I check what is causing this? Doing something like
lsof | grep -i deleted | sort -r -s -n -k 7 | head -10
gives me no clue related to any NetworkManager related… 🤷🏼♂️I'm using
python3-tracer-0.7.8-1.el8.noarch
- but also with latest release1.1
it's the same result…The text was updated successfully, but these errors were encountered: