idmapd doesnt start (wrong rpc_pipefs path)
Bug #993231 reported by
Ralph Thesen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-utils (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Using NFS4 idmapd is necessary to map the ids of nfs mounts.
/var/log/syslog says:
May 2 14:16:30 anon rpc.idmapd[1250]: main: open(/var/
May 2 14:16:30 anon kernel: [ 19.549666] init: idmapd main process (1250) terminated with status 1
May 2 14:16:30 anon kernel: [ 19.549680] init: idmapd respawning too fast, stopped
mount says:
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
Remark: on Lucid it is:
rpc_pipefs on /var/lib/
Workaround:
ln -s /run/rpc_pipefs /var/lib/
To post a comment you must log in.
You clearly aren't using the Ubuntu version of rpc.idmapd, which does use the /run/rpc_pipefs mountpoint.