Red Hat Bugzilla – Bug 817041
rpc.idmapd not started on client
Last modified: 2012-05-17 16:43:02 EDT
Description of problem:
rpc.idmapd is required to get nfsv4 to work usefully. It should
be running on *both* the client and server.
However on Fedora 17 it is not started on the client side. I
had to write an rc.local script to start it by hand:
# Fix NFS.
systemctl start var-lib-nfs-rpc_pipefs.mount
(1) sleep 10 is needed because rc.local runs too early.
(2) /var/lib/nfs/rpc_pipefs is not mounted even though the
mountpoint and service exists. No idea why.
I tried setting NEED_IDMAPD=yes in /etc/default/nfs and
/etc/default/nfs-common, but neither made any difference.
Version-Release number of selected component (if applicable):
The workaround I've been using is
systemctl enable nfs-server.service on the client.
I only need the client to be the "client" but that service starts idmapd so meh
What kernel version are you using?
With 3.3 and beyond the idmapped was changed to use a keyring based idmapping using the nfsidmap command. See nfsidmap(5) for details. With the being the cause the rpc.idmapd daemon no longer needed to be started on the NFS client.
This is arm, so it was:
Linux trim.home.annexia.org 184.108.40.206-1.0.arm1.y1.armv7hl.tegra #1 SMP PREEMPT Fri Jan 20 11:31:29 EST 2012 armv7l armv7l armv7l GNU/Linux
because there *was* a problem booting this hardware with the
newer kernel. Since (even) newer kernels are available I need
to try those.
I'll try to reboot this machine later today (currently it's running
some crucial builds).
Yes, confirmed that this does work with the later kernel.