Summary: SELinux is preventing /sbin/rpc.statd "module_request" access. Detailed Description: SELinux denied access requested by rpc.statd. It is not expected that this access is required by rpc.statd and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context system_u:system_r:rpcd_t:s0 Target Context system_u:system_r:kernel_t:s0 Target Objects None [ system ] Source rpc.statd Source Path /sbin/rpc.statd Port <Unknown> Host (removed) Source RPM Packages nfs-utils-1.2.1-1.fc12 Target RPM Packages Policy RPM selinux-policy-3.6.32-55.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.6-162.fc12.x86_64 #1 SMP Fri Dec 4 00:06:26 EST 2009 x86_64 x86_64 Alert Count 22 First Seen Wed 25 Nov 2009 08:00:59 AM IST Last Seen Wed 09 Dec 2009 10:33:43 AM IST Local ID d99c2e9a-5395-4b6c-b8e5-d0c15a47c20d Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1260335023.793:11844): avc: denied { module_request } for pid=1264 comm="rpc.statd" scontext=system_u:system_r:rpcd_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=system node=(removed) type=SYSCALL msg=audit(1260335023.793:11844): arch=c000003e syscall=41 success=no exit=-97 a0=a a1=1 a2=6 a3=7f6c10c5b210 items=0 ppid=1263 pid=1264 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="rpc.statd" exe="/sbin/rpc.statd" subj=system_u:system_r:rpcd_t:s0 key=(null) Hash String generated from selinux-policy-3.6.32-55.fc12,catchall,rpc.statd,rpcd_t,kernel_t,system,module_request audit2allow suggests: #============= rpcd_t ============== allow rpcd_t kernel_t:system module_request;
Did you disable ipv6? *** This bug has been marked as a duplicate of bug 527936 ***