Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When having the katello-host-tools-tracer package installed on the system, many processes are scanned when a yum operation is performed.
In particular it seems that arguments of these processes are collected, then stat() is issued on the arguments, which is usually non-sense:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
15160 15:09:27.340215 stat("--no-daemon", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000012>
15160 15:09:27.376073 stat("--keep-baud", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000012>
15160 15:09:27.380001 stat("--noclear", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000013>
...
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
If for some reason a process argument looks like a path name on a remote location which is not accessible (e.g. an automount), this makes the yum process hang indefinitely.
Version-Release number of selected component (if applicable):
katello-host-tools-tracer-3.5.0-2.el7sat.noarch
katello-host-tools-tracer-3.3.5-5.el7sat.noarch
How reproducible:
Always (the "dumb" stats calls at least)
Steps to Reproduce:
1. Execute the following python code
# strace -fttTvyy -o /tmp/tracer.strace -s 4096 -e stat -- python << EOF
import katello.tracer
print katello.tracer.query_affected_apps()
EOF
2. Check the strace for "ENOENT"
# grep -w ENOENT /tmp/tracer.strace | grep -v "/"
Actual results:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
...
15160 15:09:27.206950 stat("--system", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000011>
15160 15:09:27.206999 stat("--address=systemd:", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000010>
15160 15:09:27.207050 stat("--nofork", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000010>
15160 15:09:27.207092 stat("--nopidfile", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000012>
15160 15:09:27.207136 stat("--systemd-activation", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000019>
...
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Expected results:
No stat() done on process arguments, in particular if these are known remote paths
Additional info:
I don't know exactly when these stat calls are performed. It looks like this is done when updating some packages.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:4366
Description of problem: When having the katello-host-tools-tracer package installed on the system, many processes are scanned when a yum operation is performed. In particular it seems that arguments of these processes are collected, then stat() is issued on the arguments, which is usually non-sense: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 15160 15:09:27.340215 stat("--no-daemon", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000012> 15160 15:09:27.376073 stat("--keep-baud", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000012> 15160 15:09:27.380001 stat("--noclear", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000013> ... -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- If for some reason a process argument looks like a path name on a remote location which is not accessible (e.g. an automount), this makes the yum process hang indefinitely. Version-Release number of selected component (if applicable): katello-host-tools-tracer-3.5.0-2.el7sat.noarch katello-host-tools-tracer-3.3.5-5.el7sat.noarch How reproducible: Always (the "dumb" stats calls at least) Steps to Reproduce: 1. Execute the following python code # strace -fttTvyy -o /tmp/tracer.strace -s 4096 -e stat -- python << EOF import katello.tracer print katello.tracer.query_affected_apps() EOF 2. Check the strace for "ENOENT" # grep -w ENOENT /tmp/tracer.strace | grep -v "/" Actual results: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- ... 15160 15:09:27.206950 stat("--system", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000011> 15160 15:09:27.206999 stat("--address=systemd:", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000010> 15160 15:09:27.207050 stat("--nofork", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000010> 15160 15:09:27.207092 stat("--nopidfile", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000012> 15160 15:09:27.207136 stat("--systemd-activation", 0x7ffec78c75f0) = -1 ENOENT (No such file or directory) <0.000019> ... -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Expected results: No stat() done on process arguments, in particular if these are known remote paths Additional info: I don't know exactly when these stat calls are performed. It looks like this is done when updating some packages.