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.
DescriptionBrian J. Murrell
2016-09-18 16:39:49 UTC
SELinux is preventing /usr/bin/python2.7 from using the signal access on a process.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that python2.7 should be allowed signal access on processes labeled postfix_postdrop_t by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep fail2ban-server /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
Additional Information:
Source Context system_u:system_r:fail2ban_t:s0
Target Context system_u:system_r:postfix_postdrop_t:s0
Target Objects Unknown [ process ]
Source fail2ban-server
Source Path /usr/bin/python2.7
Port <Unknown>
Host server.interlinx.bc.ca
Source RPM Packages
Target RPM Packages
Policy RPM selinux-policy-3.13.1-60.el7_2.9.noarch
Selinux Enabled True
Policy Type targeted
Enforcing Mode Enforcing
Host Name server.interlinx.bc.ca
Platform Linux server.interlinx.bc.ca
3.10.0-327.28.3.el7.x86_64 #1 SMP Thu Aug 18
19:05:49 UTC 2016 x86_64 x86_64
Alert Count 33
First Seen 2016-06-27 23:23:49 EDT
Last Seen 2016-09-18 00:53:32 EDT
Local ID b1eecb90-3c8b-4024-9334-024e301c3e3b
Raw Audit Messages
type=AVC msg=audit(1474174412.129:3186): avc: denied { signal } for pid=15268 comm="fail2ban-server" scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:system_r:postfix_postdrop_t:s0 tclass=process
type=AVC msg=audit(1474174412.129:3186): avc: denied { signal } for pid=15268 comm="fail2ban-server" scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:system_r:system_mail_t:s0 tclass=process
type=SYSCALL msg=audit(1474174412.129:3186): arch=x86_64 syscall=kill success=yes exit=0 a0=ffff8ecb a1=f a2=0 a3=0 items=0 ppid=1 pid=15268 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=fail2ban-server exe=2F7573722F62696E2F707974686F6E322E373B3537646437333764202864656C6574656429 subj=system_u:system_r:fail2ban_t:s0 key=(null)
Hash: fail2ban-server,fail2ban_t,postfix_postdrop_t,process,signal
SELinux is preventing /usr/bin/python2.7 from using the signal access on a process. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that python2.7 should be allowed signal access on processes labeled postfix_postdrop_t by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep fail2ban-server /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:fail2ban_t:s0 Target Context system_u:system_r:postfix_postdrop_t:s0 Target Objects Unknown [ process ] Source fail2ban-server Source Path /usr/bin/python2.7 Port <Unknown> Host server.interlinx.bc.ca Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-60.el7_2.9.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name server.interlinx.bc.ca Platform Linux server.interlinx.bc.ca 3.10.0-327.28.3.el7.x86_64 #1 SMP Thu Aug 18 19:05:49 UTC 2016 x86_64 x86_64 Alert Count 33 First Seen 2016-06-27 23:23:49 EDT Last Seen 2016-09-18 00:53:32 EDT Local ID b1eecb90-3c8b-4024-9334-024e301c3e3b Raw Audit Messages type=AVC msg=audit(1474174412.129:3186): avc: denied { signal } for pid=15268 comm="fail2ban-server" scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:system_r:postfix_postdrop_t:s0 tclass=process type=AVC msg=audit(1474174412.129:3186): avc: denied { signal } for pid=15268 comm="fail2ban-server" scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:system_r:system_mail_t:s0 tclass=process type=SYSCALL msg=audit(1474174412.129:3186): arch=x86_64 syscall=kill success=yes exit=0 a0=ffff8ecb a1=f a2=0 a3=0 items=0 ppid=1 pid=15268 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=fail2ban-server exe=2F7573722F62696E2F707974686F6E322E373B3537646437333764202864656C6574656429 subj=system_u:system_r:fail2ban_t:s0 key=(null) Hash: fail2ban-server,fail2ban_t,postfix_postdrop_t,process,signal