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:
I found this in my audit.log:
type=AVC msg=audit(1328730010.816:41): avc: denied { read write } for pid=2438 comm="consoletype" path="socket:[13102]" dev=sockfs ino=13102 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:system_r:initrc_t:s0 tclass=udp_socket
I'm guessing there's a leaked file descriptor from something that called consoletype.
Version-Release number of selected component (if applicable):
This is owned by initscripts version 9.03.27-1
How reproducible:
No idea. Found it in a log. Never saw it before. I also can't figure out who called consoletype to find out who might be leaking a file descriptor.
Not really, sorry. This appears to have happened at boot time, and from the message, it looks to have been called by an init script. Does the init system use file system sockets?
I also haven't seen this repeat. I'm thinking about filing a feature request with SELinux to have the reports include the parent PID and command name. That might be helpful sometimes.
Comment 9RHEL Program Management
2012-07-10 08:20:27 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 10RHEL Program Management
2012-07-11 01:55:17 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Description of problem: I found this in my audit.log: type=AVC msg=audit(1328730010.816:41): avc: denied { read write } for pid=2438 comm="consoletype" path="socket:[13102]" dev=sockfs ino=13102 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_u:system_r:initrc_t:s0 tclass=udp_socket I'm guessing there's a leaked file descriptor from something that called consoletype. Version-Release number of selected component (if applicable): This is owned by initscripts version 9.03.27-1 How reproducible: No idea. Found it in a log. Never saw it before. I also can't figure out who called consoletype to find out who might be leaking a file descriptor.