Hide Forgot
SELinux is preventing /sbin/chkconfig from 'read' accesses on the file cgred. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that chkconfig should be allowed read access on the cgred 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 chkconfig /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:gnomeclock_t:s0-s0:c0.c1023 Target Context system_u:object_r:cgred_initrc_exec_t:s0 Target Objects cgred [ file ] Source chkconfig Source Path /sbin/chkconfig Port <Unknown> Host (removed) Source RPM Packages chkconfig-1.3.49-2.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.14-2.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.38-0.rc5.git1.1.fc15.x86_64 #1 SMP Thu Feb 17 01:49:02 UTC 2011 x86_64 x86_64 Alert Count 1 First Seen Thu 07 Apr 2011 03:56:06 AM CEST Last Seen Thu 07 Apr 2011 03:56:06 AM CEST Local ID 8c596bab-ecb5-495b-8bee-042e3ec1d752 Raw Audit Messages type=AVC msg=audit(1302141366.188:606): avc: denied { read } for pid=4822 comm="chkconfig" name="cgred" dev=sda1 ino=142213 scontext=system_u:system_r:gnomeclock_t:s0-s0:c0.c1023 tcontext=system_u:object_r:cgred_initrc_exec_t:s0 tclass=file type=SYSCALL msg=audit(1302141366.188:606): arch=x86_64 syscall=open success=no exit=EACCES a0=234d0d0 a1=0 a2=0 a3=0 items=0 ppid=4784 pid=4822 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=chkconfig exe=/sbin/chkconfig subj=system_u:system_r:gnomeclock_t:s0-s0:c0.c1023 key=(null) Hash: chkconfig,gnomeclock_t,cgred_initrc_exec_t,file,read audit2allow #============= gnomeclock_t ============== allow gnomeclock_t cgred_initrc_exec_t:file read; audit2allow -R #============= gnomeclock_t ============== allow gnomeclock_t cgred_initrc_exec_t:file read;
*** This bug has been marked as a duplicate of bug 675278 ***