Hide Forgot
SELinux is preventing /usr/bin/python from 'write' accesses on the sock_file setroubleshoot_server. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that python should be allowed write access on the setroubleshoot_server sock_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 sealert /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context staff_u:staff_r:staff_t:s0-s0:c0.c1023 Target Context system_u:object_r:tmpfs_t:s0 Target Objects setroubleshoot_server [ sock_file ] Source sealert Source Path /usr/bin/python Port <Neznámé> Host (removed) Source RPM Packages python-2.7.1-6.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-6.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 2.6.38.2-9.fc15.x86_64 #1 SMP Wed Mar 30 16:55:57 UTC 2011 x86_64 x86_64 Alert Count 1 First Seen Pá 1. duben 2011, 16:30:26 CEST Last Seen Pá 1. duben 2011, 16:30:26 CEST Local ID d532bb25-0a58-4d60-bdbd-898f61e54ae6 Raw Audit Messages type=AVC msg=audit(1301668226.899:6325): avc: denied { write } for pid=15535 comm="sealert" name="setroubleshoot_server" dev=tmpfs ino=711185 scontext=staff_u:staff_r:staff_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmpfs_t:s0 tclass=sock_file type=SYSCALL msg=audit(1301668226.899:6325): arch=x86_64 syscall=connect success=yes exit=0 a0=a a1=7fff1c432b60 a2=2f a3=2f746f6f6873656c items=0 ppid=1 pid=15535 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=140 comm=sealert exe=/usr/bin/python subj=staff_u:staff_r:staff_t:s0-s0:c0.c1023 key=(null) Hash: sealert,staff_t,tmpfs_t,sock_file,write audit2allow #============= staff_t ============== allow staff_t tmpfs_t:sock_file write; audit2allow -R #============= staff_t ============== allow staff_t tmpfs_t:sock_file write;
*** This bug has been marked as a duplicate of bug 692459 ***