Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 I execute lsof on some systems, it doesn't report that certain file descriptors are sockets and what types of sockets (all are reported "unknown"), on others it works as expected.
Version-Release number of selected component (if applicable):
lsof-4.94.0-3.el9.x86_64
How reproducible:
when it happens, it's fully reproducible, but not on all systems
Steps to Reproduce:
1. provision machine in 1minutetip
2. ps aux | grep sshd
3. lsof -w -b -p $sshd_pid
Actual results:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sshd 3456 root cwd unknown /
sshd 3456 root rtd unknown /
sshd 3456 root txt unknown /usr/sbin/sshd
sshd 3456 root mem REG 253,1 6753911 /usr/sbin/sshd
sshd 3456 root mem REG 253,1 6522798 /usr/lib64/libnss_systemd.so.2
sshd 3456 root mem REG 253,1 6709939 /usr/lib64/libnss_sss.so.2
sshd 3456 root mem REG 253,1 4759913 /usr/lib64/security/pam_lastlog.so
...
sshd 3456 root mem REG 253,1 6394687 /usr/lib64/ld-linux-x86-64.so.2
sshd 3456 root mem REG 0,20 19 /sys/fs/selinux/status
sshd 3456 root 0 unknown /dev/null
sshd 3456 root 1 unknown /dev/null
sshd 3456 root 2 unknown /dev/null
sshd 3456 root 3 unknown socket
sshd 3456 root 4 unknown socket
sshd 3456 root 5 unknown /dev/ptmx
sshd 3456 root 6 unknown socket
sshd 3456 root 7 unknown /run/systemd/sessions/3.ref
sshd 3456 root 8 unknown socket
Expected results:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sshd 6164 root cwd DIR 253,1 4096 2 /
sshd 6164 root rtd DIR 253,1 4096 2 /
sshd 6164 root txt REG 253,1 952568 3937467 /usr/sbin/sshd
sshd 6164 root mem REG 253,1 6940392 1445554 /var/lib/sss/mc/group
...
sshd 6164 root mem REG 253,1 135256 3995397 /usr/lib64/libaudit.so.1.0.0
sshd 6164 root mem REG 253,1 843032 3937850 /usr/lib64/ld-2.33.so
sshd 6164 root 0r CHR 1,3 0t0 4 /dev/null
sshd 6164 root 1u unix 0x0000000090427bf4 0t0 45521 type=STREAM (CONNECTED)
sshd 6164 root 2u unix 0x0000000090427bf4 0t0 45521 type=STREAM (CONNECTED)
sshd 6164 root 3r REG 253,1 9253600 1445549 /var/lib/sss/mc/passwd
sshd 6164 root 4u unix 0x00000000967d618d 0t0 38647 type=STREAM (CONNECTED)
sshd 6164 root 5u IPv4 45537 0t0 TCP *:ssh (LISTEN)
sshd 6164 root 6r REG 253,1 6940392 1445554 /var/lib/sss/mc/group
sshd 6164 root 7u IPv6 45539 0t0 TCP *:ssh (LISTEN)
Additional info:
Comment 4RHEL Program Management
2023-09-21 09:55:42 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5RHEL Program Management
2023-09-21 09:55:56 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.