Hide Forgot
Just installed f26 server and nfs-server failed to start. Think it's a selinux problem. audit[2875]: AVC avc: denied { create } for pid=2875 comm="systemd-tmpfile" name="rpcbind" scontext=system_u:system_r:rpcbind_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=dir per systemd-tmpfiles[2875]: Failed to create directory or subvolume "/run/rpcbind": Permission denied rpcbind[2874]: rpcbind: /run/rpcbind/rpcbind.lock: No such file or directory systemd[1]: rpcbind.service: Main process exited, code=exited, status=1/FAILURE
Is rpcbind running systemd-tmpfile?
I think so. F26 has 3.13.1-260.1 and the changelog has this: * Mon Jun 19 2017 Lukas Vrabec <lvrabec@redhat.com> - 3.13.1-258 - Allow rpcbind_t to execute systemd_tmpfiles_exec_t binary files.
This only happens on fresh installs. When /run/rpcbind does not yet exist. I placed the system in permissive mode, started the service and everything started fine. /run/rpcbind was created. Back in enforcing mode the service starts and stops fine, even through reboots.
(In reply to louisgtwo from comment #3) > This only happens on fresh installs. When /run/rpcbind does not yet exist. I > placed the system in permissive mode, started the service and everything > started fine. /run/rpcbind was created. Back in enforcing mode the service > starts and stops fine, even through reboots. I can confirm what louisgtwo has said. This issue totally breaks the Fedora 26 Cloud Base Images for Vagrant. You can't use NFS out of the box.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.