Hide Forgot
SELinux is preventing /usr/bin/python from 'execute' accesses on the file /tmp/ffiFTB4rf (deleted). ***** Plugin catchall (100. confidence) suggests *************************** If you believe that python should be allowed execute access on the ffiFTB4rf (deleted) file 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:object_r:tmp_t:s0 Target Objects /tmp/ffiFTB4rf (deleted) [ file ] Source fail2ban-server Source Path /usr/bin/python Port <Unknown> Host (removed) Source RPM Packages python-2.7-8.fc14.1 Target RPM Packages Policy RPM selinux-policy-3.9.7-42.fc14 Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 2.6.35.13-92.fc14.i686.PAE #1 SMP Sat May 21 17:33:09 UTC 2011 i686 i686 Alert Count 4 First Seen Tue 14 Jun 2011 10:20:49 PM CEST Last Seen Mon 25 Jul 2011 09:36:12 PM CEST Local ID 7249a8f0-5bea-4840-926a-28c3c32dbf3f Raw Audit Messages type=AVC msg=audit(1311622572.223:20): avc: denied { execute } for pid=1982 comm="fail2ban-server" path=2F746D702F666669465442347266202864656C6574656429 dev=dm-1 ino=3145732 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:tmp_t:s0 tclass=file type=SYSCALL msg=audit(1311622572.223:20): arch=i386 syscall=mmap2 success=yes exit=10661888 a0=0 a1=1000 a2=5 a3=1 items=0 ppid=1 pid=1982 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=/usr/bin/python subj=system_u:system_r:fail2ban_t:s0 key=(null) Hash: fail2ban-server,fail2ban_t,tmp_t,file,execute audit2allow #============= fail2ban_t ============== allow fail2ban_t tmp_t:file execute; audit2allow -R #============= fail2ban_t ============== allow fail2ban_t tmp_t:file execute;
*** Bug 725545 has been marked as a duplicate of this bug. ***
Why is fail2ban executing random content in /tmp?