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

[Anders Larsson]

You're correct. If I install nfs-common manually it will automatically
start run-rpc_pipefs.mount and the mount point exists. I'm not sure what
is happening.

I did some additional testing and we're not directly installing nfs-
common but installing autofs which pulls in nfs-common. After I had
tested this I did `apt-get purge autofs nfs-common` and did `apt-get
install autofs` and run-rpc_pipefs.mount is not automatically started.
This could of course be because it was installed and then purged which
caused some issue. I'll reinstall the system again and try installing
autofs and see what happens.

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