Hide Forgot
SELinux is preventing /sbin/consoletype from 'read' accesses on the lnk_file current. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that consoletype should be allowed read access on the current lnk_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 consoletype /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:system_r:consoletype_t:s0 Target Context system_u:object_r:nfs_t:s0 Target Objects current [ lnk_file ] Source consoletype Source Path /sbin/consoletype Port <Unknown> Host (removed) Source RPM Packages initscripts-9.20.2-1.fc14.1 Target RPM Packages Policy RPM selinux-policy-3.9.7-37.fc14 Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 2.6.35.11-83.fc14.x86_64 #1 SMP Mon Feb 7 07:06:44 UTC 2011 x86_64 x86_64 Alert Count 1 First Seen Fri 25 Mar 2011 10:26:44 AM EDT Last Seen Fri 25 Mar 2011 10:26:44 AM EDT Local ID 9715fbc8-a086-488a-9aa0-d32a5ac14b28 Raw Audit Messages type=AVC msg=audit(1301063204.59:3190712): avc: denied { read } for pid=16010 comm="consoletype" name="current" dev=afs ino=12084124 scontext=unconfined_u:system_r:consoletype_t:s0 tcontext=system_u:object_r:nfs_t:s0 tclass=lnk_file type=SYSCALL msg=audit(1301063204.59:3190712): arch=x86_64 syscall=open success=no exit=ENOENT a0=7fffde61bd30 a1=0 a2=0 a3=402f626466772f65 items=0 ppid=16009 pid=16010 auid=768 uid=768 gid=1002 euid=768 suid=768 fsuid=768 egid=1002 sgid=1002 fsgid=1002 tty=pts1 ses=4 comm=consoletype exe=/sbin/consoletype subj=unconfined_u:system_r:consoletype_t:s0 key=(null) Hash: consoletype,consoletype_t,nfs_t,lnk_file,read audit2allow #============= consoletype_t ============== allow consoletype_t nfs_t:lnk_file read; audit2allow -R #============= consoletype_t ============== allow consoletype_t nfs_t:lnk_file read;
Do you know what you were doing when this happened?
Looks like a leak.
Yes, please reopen the bug if the bug still exists.