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.
DescriptionOrion Poplawski
2017-11-14 18:26:56 UTC
Description of problem:
With SELinux enforcing, fail2ban is limited to 1024 open files. In permissive it is set to whatever LimitNOFILE is set to.
I don't see any AVCs though, perhaps they are not audited.
Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-166.el7_4.5.noarch
Please attach the list of SELinux denials that appear in your scenario. My guess is that the list will contain an { setrlimit } AVC.
# ausearch -m avc -m user_avc -m selinux_err -m user_selinux_err -i -ts today
Created attachment 1352713[details]
ausearch output
This seems really odd to me. Here are messages with dontaudit disabled. But I'm not seeing anything obvious. But I definitely have to be in permissive mode for the file limit to be increased.
Specifically:
type=AVC msg=audit(1510761934.613:358117): avc: denied { rlimitinh } for pid=15602 comm="fail2ban-server" scontext=system_u:system_r:fail2ban_client_t:s0 tcontext=system_u:system_r:fail2ban_t:s0 tclass=process
since the server is started via fail2ban-client:
# grep Exec /usr/lib/systemd/system/fail2ban.service
ExecStart=/usr/bin/fail2ban-client -x start
ExecStop=/usr/bin/fail2ban-client stop
ExecReload=/usr/bin/fail2ban-client reload
This seems to do the trick:
module fail2ban-rlimit 1.0;
require {
type fail2ban_client_t;
type fail2ban_t;
class process { rlimitinh };
}
allow fail2ban_client_t fail2ban_t:process { rlimitinh };
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, 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/RHBA-2018:3111