[Bug 993231] Re: idmapd doesnt start (wrong rpc_pipefs path)

[Steve Langasek]

Actually, there's another possibility: you may have Pipefs-Directory set
to the wrong place in /etc/idmapd.conf.  The correct default
/etc/idmapd.conf, as shipped by nfs-common, is:

[General]

Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
# set your own domain here, if id differs from FQDN minus hostname
# Domain = localdomain

[Mapping]

Nobody-User = nobody
Nobody-Group = nogroup

So you may have opted to "keep your version" of the config file on
upgrade, which in this particular case results in a broken config.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/993231

Title:
  idmapd doesnt start (wrong rpc_pipefs path)

Status in “nfs-utils” package in Ubuntu:
  New

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/lib/nfs/rpc_pipefs/nfs): No such file or directory
  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/nfs/rpc_pipefs type rpc_pipefs (rw)

  Workaround:

  ln -s /run/rpc_pipefs /var/lib/nfs/rpc_pipefs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/993231/+subscriptions