[Bug 1428961] Re: idmapd not started when booting under systemd

[ganrald]

Please don't kill me if I was supposed to create a new bug report rather
than update this one.

This bug is still present in Ubuntu 15.10 (Wily Werewolf).

My Ubuntu NFS client is working fine, apart from the fact that no idmapd
is running.

# pgrep idmap
#

# dpkg-query -W nfs-common
nfs-common      1:1.2.8-9ubuntu10

# systemctl status nfs-idmapd
● nfs-idmapd.service - NFSv4 ID-name mapping service
   Loaded: loaded (/lib/systemd/system/nfs-idmapd.service; static; vendor preset: enabled)
   Active: inactive (dead)

# systemctl start nfs-idmapd
Failed to start nfs-idmapd.service: Unit nfs-server.service failed to load: No such file or directory.

I don't have nfs-kernel-server package installed and the dependency is
still present in /lib/systemd/system/nfs-idmapd.service file

# grep BindsTo /lib/systemd/system/nfs-idmapd.service
BindsTo=nfs-server.service

I have one more remark in http://www.spinics.net/lists/linux-
nfs/msg49996.html Steve mentions that you want to use nfsidmap, however
the nfs-idmapd.service unit file starts rpc.idmapd.

# grep ExecStart /lib/systemd/system/nfs-idmapd.service
ExecStart=/usr/sbin/rpc.idmapd $RPCIDMAPDARGS


** Tags added: wily

-- 
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/1428961

Title:
  idmapd not started when booting under systemd

Status in nfs-utils package in Ubuntu:
  Fix Released

Bug description:
  Sorry for not getting a chance to test this before upload, but now
  that nfs-utils has support for systemd in the archive, I've rebooted
  and tested it on a system that uses nfs.

  I find that the idmapd service is not being started on boot when
  booting with systemd.

  $ pidof rpc.idmapd
  $ systemctl status nfs-idmapd -l
  ● nfs-idmapd.service - NFSv4 ID-name mapping service
     Loaded: loaded (/lib/systemd/system/nfs-idmapd.service; static; vendor preset: enabled)
     Active: inactive (dead)

  Mar 05 22:31:24 virgil systemd[1]: Starting NFSv4 ID-name mapping service...
  Mar 05 22:31:24 virgil systemd[1]: Started NFSv4 ID-name mapping service.
  Mar 05 22:31:24 virgil systemd[1]: Unit nfs-idmapd.service is bound to inactive unit. Stopping, too.
  Mar 05 22:31:24 virgil systemd[1]: Stopping NFSv4 ID-name mapping service...
  Mar 05 22:31:24 virgil systemd[1]: Stopped NFSv4 ID-name mapping service.
  $

  Under upstart, it is started unconditionally, which is correct.
  idmapd is used on both clients and servers, and should be started
  whenever the nfs-common package is installed.

  I'm not sure where the bug lies; I don't completely understand the
  contents of /lib/systemd/system/nfs-idmapd.service.  The 'BindsTo=nfs-
  server.service' appears to be imply that it will only be started when
  nfs-server is started, and stopped when nfs-server is stopped, which
  is certainly incorrect.

  gssd is client-side only; idmapd and statd are used on both client and
  server and should be started unconditionally in nfs-common, AIUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nfs-common 1:1.2.8-9ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  5 22:36:57 2015
  InstallationDate: Installed on 2010-09-24 (1624 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
  SourcePackage: nfs-utils
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (90 days ago)

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