rpcbind service can't start up automatically by mounting a NFSv3 file system after "systemctl isolate"
rpcbind.service does not start automatically by mounting a NFSv3 file system after "systemctl isolate graphical.target"
or "systemctl isolate multi-user.target". Until starting rpcbind.service manually, mounting NFSv3 file systems fails with
the following messages even though rpc-statd.service is active (running).
mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified
- Red Hat Enterprise Linux 7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.