Hide Forgot
Description of problem: Started by automated run of prelink. SELinux is preventing /usr/sbin/prelink from 'write' accesses on the directory /usr/libexec. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that prelink should be allowed write access on the libexec 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 prelink /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:prelink_cron_system_t:s0-s0:c0.c 1023 Target Context system_u:object_r:bin_t:s0 Target Objects /usr/libexec [ dir ] Source prelink Source Path /usr/sbin/prelink Port <Unknown> Host (removed) Source RPM Packages prelink-0.5.0-1.fc20.x86_64 Target RPM Packages filesystem-3.2-19.fc20.x86_64 Policy RPM selinux-policy-3.12.1-106.fc20.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.11.10-300.fc20.x86_64 #1 SMP Fri Nov 29 19:16:48 UTC 2013 x86_64 x86_64 Alert Count 5 First Seen 2013-12-11 09:45:06 EST Last Seen 2013-12-11 09:45:06 EST Local ID fdc623f4-0e58-4c1e-ab1b-880dcf3004ad Raw Audit Messages type=AVC msg=audit(1386773106.373:2866): avc: denied { write } for pid=26155 comm="prelink" name="libexec" dev="dm-1" ino=2228233 scontext=system_u:system_r:prelink_cron_system_t:s0-s0:c0.c1023 tcontext=system_u:object_r:bin_t:s0 tclass=dir type=SYSCALL msg=audit(1386773106.373:2866): arch=x86_64 syscall=open success=no exit=EACCES a0=7fffbf19d1b0 a1=c2 a2=180 a3=20 items=0 ppid=26146 pid=26155 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=49 tty=(none) comm=prelink exe=/usr/sbin/prelink subj=system_u:system_r:prelink_cron_system_t:s0-s0:c0.c1023 key=(null) Hash: prelink,prelink_cron_system_t,bin_t,dir,write Additional info: reporter: libreport-2.1.9 hashmarkername: setroubleshoot kernel: 3.11.10-300.fc20.x86_64 type: libreport
*** This bug has been marked as a duplicate of bug 1040515 ***