Hide Forgot
SELinux is preventing /usr/bin/python from 'write' accesses on the sock_file abrt.socket. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that python should be allowed write access on the abrt.socket 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 pyzor /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:spamc_t:s0 Target Context system_u:object_r:abrt_var_run_t:s0 Target Objects abrt.socket [ sock_file ] Source pyzor Source Path /usr/bin/python Port <Inconnu> Host (removed) Source RPM Packages python-2.7.2-4.fc16 Target RPM Packages Policy RPM selinux-policy-3.10.0-2.fc16 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.0-0.rc6.git0.1.fc16.x86_64 #1 SMP Tue Jul 5 00:39:12 UTC 2011 x86_64 x86_64 Alert Count 27 First Seen lun. 27 juin 2011 22:18:33 CEST Last Seen sam. 09 juil. 2011 13:28:47 CEST Local ID 975b9e8b-c527-4746-bbc5-a93fbedb753f Raw Audit Messages type=AVC msg=audit(1310210927.165:14): avc: denied { write } for pid=1353 comm="pyzor" name="abrt.socket" dev=tmpfs ino=15871 scontext=system_u:system_r:spamc_t:s0 tcontext=system_u:object_r:abrt_var_run_t:s0 tclass=sock_file type=SYSCALL msg=audit(1310210927.165:14): arch=x86_64 syscall=connect success=no exit=EACCES a0=4 a1=7fff79622f00 a2=1b a3=6e75722f7261762f items=0 ppid=1347 pid=1353 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=pyzor exe=/usr/bin/python subj=system_u:system_r:spamc_t:s0 key=(null) Hash: pyzor,spamc_t,abrt_var_run_t,sock_file,write audit2allow #============= spamc_t ============== allow spamc_t abrt_var_run_t:sock_file write; audit2allow -R #============= spamc_t ============== allow spamc_t abrt_var_run_t:sock_file write;
Do you know when this happened? During a crash?
Yes, python uses abrt.socket to communicate with abrtd and abrtd then stores informations received. It works that way quite a long time, so I suspect something has changed in the selinux policy.
Of course. Please forget on it.
Fixed in selinux-policy-3.10.0-3.fc16