Description of problem: tried to mount an nfs share like this: sudo mount -t nfs nas:/data/ ~/nas/ SELinux is preventing rpc.statd from 'write' accesses on the file rpc.statd.pid. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that rpc.statd should be allowed write access on the rpc.statd.pid 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 rpc.statd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:rpcd_t:s0 Target Context unconfined_u:object_r:var_run_t:s0 Target Objects rpc.statd.pid [ file ] Source rpc.statd Source Path rpc.statd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-116.fc22.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.0.0-0.rc2.git0.1.fc22.x86_64 #1 SMP Tue Mar 3 21:24:17 UTC 2015 x86_64 x86_64 Alert Count 1 First Seen 2015-03-11 15:10:28 CET Last Seen 2015-03-11 15:10:28 CET Local ID fdd59843-44d4-43de-8fc4-e7e25608aad4 Raw Audit Messages type=AVC msg=audit(1426083028.493:843): avc: denied { write } for pid=7101 comm="rpc.statd" name="rpc.statd.pid" dev="tmpfs" ino=102698 scontext=system_u:system_r:rpcd_t:s0 tcontext=unconfined_u:object_r:var_run_t:s0 tclass=file permissive=0 Hash: rpc.statd,rpcd_t,var_run_t,file,write Version-Release number of selected component: selinux-policy-3.13.1-116.fc22.noarch Additional info: reporter: libreport-2.4.0 hashmarkername: setroubleshoot kernel: 4.0.0-0.rc2.git0.1.fc22.x86_64 type: libreport Potential duplicate: bug 750103
Have you ever started rpcd directly? # restorecon -R -v /var/run/rpc* Should fix your issue. If I am wrong, please reopen the bug. Thank you.
I'm having this exact same issue. Fresh install of server and the above doesn't solve it.
(In reply to adalan from comment #2) > I'm having this exact same issue. Fresh install of server and the above > doesn't solve it. What AVC are you getting?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days