You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After succefully joining an host using linupdate and repomanager, I saw a high CPU load (50%) on my host, after checking "top" for used process, I saw DNF so no worries for now, seems like standard usage when DNF is checking packages.
30 minutes later CPU usage still at 50% and DNF is still doing things, after logs inspection I can see linupdate looping through dnf history to get linupdate package history (I guess ?), my host is pretty old so maybe with the amount of logs it's normal (Over 200).
Later I can then see that it started looking for logs history non stop, after reaching my latest logs (n°200 or so) it started looping again from logs n°1
How can I prevent that bug ? Maybe is it possible to add an option to look only for the last 10 logs or so ? It looped over logs at least twice now
SPECS :
OS: Red Hat Enterprise Linux release 8.10 (Ootpa) x86_64
Host: VMware7,1
Kernel: 4.18.0-553.22.1.el8_10.x86_64
Uptime: 27 days, 33 mins
The text was updated successfully, but these errors were encountered:
Okay I will have to do some tests again with a RHEL 8 host. I think this is an issue with the latest version. For now you can stop the linupdate service to avoid this behavior:
systemctl stop linupdate
I'll reach you through discord for additional tests.
Thanks
Hi again,
After succefully joining an host using linupdate and repomanager, I saw a high CPU load (50%) on my host, after checking "top" for used process, I saw DNF so no worries for now, seems like standard usage when DNF is checking packages.
30 minutes later CPU usage still at 50% and DNF is still doing things, after logs inspection I can see linupdate looping through dnf history to get linupdate package history (I guess ?), my host is pretty old so maybe with the amount of logs it's normal (Over 200).
Later I can then see that it started looking for logs history non stop, after reaching my latest logs (n°200 or so) it started looping again from logs n°1
How can I prevent that bug ? Maybe is it possible to add an option to look only for the last 10 logs or so ? It looped over logs at least twice now
SPECS :
OS: Red Hat Enterprise Linux release 8.10 (Ootpa) x86_64
Host: VMware7,1
Kernel: 4.18.0-553.22.1.el8_10.x86_64
Uptime: 27 days, 33 mins
The text was updated successfully, but these errors were encountered: