[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

[Andreas Hasenack]

> up until just before the step to install and manage the NFS stuff and rpc_pipefs is not mounted 
> anywhere before starting to configure NFS+Kerberos with Puppet for the first time.

Are you saying that on a jammy system, after "sudo apt install nfs-
common", you don't get rpc_pipefs mounted?

Right after installing nfs-common, I have it:

(...)
Setting up nfs-common (1:2.6.1-1ubuntu1) ...

Creating config file /etc/idmapd.conf with new version

Creating config file /etc/nfs.conf with new version
Adding system user `statd' (UID 112) ...
Adding new user `statd' (UID 112) with group `nogroup' ...
Not creating home directory `/var/lib/nfs'.
Created symlink /etc/systemd/system/multi-user.target.wants/nfs-client.target → /lib/systemd/system/nfs-client.target.
Created symlink /etc/systemd/system/remote-fs.target.wants/nfs-client.target → /lib/systemd/system/nfs-client.target.
auth-rpcgss-module.service is a disabled or a static unit, not starting it.
nfs-idmapd.service is a disabled or a static unit, not starting it.
nfs-utils.service is a disabled or a static unit, not starting it.
proc-fs-nfsd.mount is a disabled or a static unit, not starting it.
rpc-gssd.service is a disabled or a static unit, not starting it.
rpc-statd-notify.service is a disabled or a static unit, not starting it.
rpc-statd.service is a disabled or a static unit, not starting it.
rpc-svcgssd.service is a disabled or a static unit, not starting it.
rpc_pipefs.target is a disabled or a static unit, not starting it.
var-lib-nfs-rpc_pipefs.mount is a disabled or a static unit, not starting it.
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3) ...

ubuntu at j-nfs:~$ mount -t rpc_pipefs
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)


And it was the generator that did it, as expected:

ubuntu at j-nfs:~$ systemctl status run-rpc_pipefs.mount 
● run-rpc_pipefs.mount - RPC Pipe File System
     Loaded: loaded (/run/systemd/generator/run-rpc_pipefs.mount; generated)
     Active: active (mounted) since Fri 2022-07-01 12:20:29 UTC; 4min 45s ago
      Where: /run/rpc_pipefs
       What: sunrpc
      Tasks: 0 (limit: 1119)
     Memory: 20.0K
        CPU: 1ms
     CGroup: /system.slice/run-rpc_pipefs.mount

Jul 01 12:20:29 j-nfs systemd[1]: Mounting RPC Pipe File System...
Jul 01 12:20:29 j-nfs systemd[1]: Mounted RPC Pipe File System.

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

Title:
  Invalid pipefs-directory prevents rpc-gssd.service from starting

Status in nfs-utils package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 Server
  Package version: 1:2.6.1-1ubuntu1

  Package nfs-common/nfs-utils provides /etc/nfs.conf and /lib/systemd/system/rpc-gssd.service.
  /etc/nfs.conf (and seems to be copied from /usr/share/nfs-common/conffiles/nfs.conf) has the configuration:
  ...
  [general]
  pipefs-directory=/run/rpc_pipefs
  ...

  When attempting to start rpc-gssd it gives the following error:
  ...
  ERROR: opendir(/run/rpc_pipefs) failed: No such file or directory
  ...

  There is a systemd unit called var-lib-nfs-rpc_pipefs.mount which
  mounts this directory as /var/lib/nfs/rpc_pipefs. However this does
  not match with the configuration in nfs.conf

  It's worth mentioning that sometimes it seems a systemd unit is
  generated (run-rpc_pipefs.mount) which ensures /run/rpc_pipefs is
  created and everything works as expected. Seems to be random.

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