rpc.statd not started automatically
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-utils (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hello,
I've noticed that if my NFS mounts do not have the 'auto' option, rpc.statd does not start automatically, without a password.
When I try to mount the share, I'm prompted for the sudo password, in order to start rpc.statd:
> Authentication is required to start 'rpc-statd.
If the current user does not know the password, he cannot start rpc.statd and thus cannot mount the share.
Here is a sample session:
$ mount /media/xxx
[a popup window opens to prompt for a password, choose "cancel"]
Failed to start rpc-statd.service: Access denied
See system logs and 'systemctl status rpc-statd.service' for details.
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
/var/log/syslog contains:
Sep 17 20:22:41 mcqueen rpc.statd[5160]: Opening /run/rpc.statd.pid failed: Permission denied
$ systemctl status rpc-statd.service
● rpc-statd.service - NFS status monitor for NFSv2/3 locking.
Loaded: loaded (/lib/systemd/
Active: inactive (dead)
/etc/fstab entry:
192.168.
Of course, if I enter the sudo password, or if I manually start rpc.statd as root before trying to mount, the mount operation succeeds.
Similarly, if I replace "noauto" with "auto", rpc.statd is started during the boot sequence, and everything works.
Yet, I'd expect that any user be able to mount this share, since it has the "user" option.
Problem currently noticed with ubuntu 16.04.
nfs-common:
Installed: 1:1.2.8-9ubuntu12
Candidate: 1:1.2.8-9ubuntu12
Version table:
*** 1:1.2.8-9ubuntu12 500
500 http://
100 /var/lib/
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.