Hide Forgot
Description of problem: SELinux is preventing /usr/bin/python2.7 from 'write' accesses on the directory /var/log. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that python2.7 should be allowed write access on the log directory 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 python /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:sosreport_t:s0-s0:c0.c1023 Target Context system_u:object_r:var_log_t:s0 Target Objects /var/log [ dir ] Source python Source Path /usr/bin/python2.7 Port <Unknown> Host (removed) Source RPM Packages python-2.7.5-10.el7.x86_64 Target RPM Packages filesystem-3.2-14.el7.x86_64 Policy RPM selinux-policy-3.12.1-105.el7.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.10.0-54.el7.x86_64 #1 SMP Thu Nov 21 15:34:15 EST 2013 x86_64 x86_64 Alert Count 1 First Seen 2013-12-02 08:35:42 MST Last Seen 2013-12-02 08:35:42 MST Local ID 442e9db9-eb4f-4bfb-8be9-99508c329af2 Raw Audit Messages type=AVC msg=audit(1385998542.835:17601): avc: denied { write } for pid=28477 comm="python" name="log" dev="dm-2" ino=2359330 scontext=system_u:system_r:sosreport_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_log_t:s0 tclass=dir type=SYSCALL msg=audit(1385998542.835:17601): arch=x86_64 syscall=open success=no exit=EACCES a0=39e8750 a1=441 a2=1b6 a3=39eaa30 items=0 ppid=28476 pid=28477 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=python exe=/usr/bin/python2.7 subj=system_u:system_r:sosreport_t:s0-s0:c0.c1023 key=(null) Hash: python,sosreport_t,var_log_t,dir,write Additional info: reporter: libreport-2.1.7 hashmarkername: setroubleshoot kernel: 3.10.0-54.el7.x86_64 type: libreport
I believe this bug is a duplicate of bz#1032629.
*** This bug has been marked as a duplicate of bug 1032629 ***