[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade

[Charles Hedrick]

right. It's not failing. It's not running at all.

systemctl status rpc-statd
● rpc-statd.service - NFS status monitor for NFSv2/3 locking.
     Loaded: loaded (/lib/systemd/system/rpc-statd.service; disabled; vendor preset: enabled)
     Active: inactive (dead)

Journalctl doesn't show that nfs-utils ran. As far as I can tell, that's
the only thing that would activate it.

I note that there's an [Install] section in rpc-statd.service. That
implies that it's intended to be enabled. It's not. If you enable it,
everything works. I suspected maybe the upgrade was supposed to enable
it but didn't.

rpc.statd version 1.3.3

ls -l /sbin/rpc.statd 
-rwxr-xr-x 1 root root 89016 May 24  2021 /sbin/rpc.statd

ls -lc /sbin/rpc.statd
-rwxr-xr-x 1 root root 89016 Jan 10 15:09 /sbin/rpc.statd

It looks like it changed in the last update. It was "apt upgrade"

/etc/default/nfs-common 
STATDOPTS=
NEED_GSSD=yes

/etc/default/nfs-kernel-server
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD="yes"
RPCSVCGSSDOPTS=""

/etc/default/rpcbind 
OPTIONS=""
OPTIONS="-w"

/etc/systemd/system/rpc-gssd.service.d
gss-krb.conf 
[Service]
Environment=KRB5_CONFIG=/etc/krb5.conf:/etc/krb5.conf.gssd

time.conf
[Service]
Environment=GSSDARGS=-t600

The KRB5_CONFIG is to configure 
[plugins]
  ccselect = {
     module = nfs:/usr/lib/ccselect_nfs.so
  }
ccselect_nfs.so selects the user's primary principal, so that if they've done kinit as user.admin to do privileged stuff, NFS still uses their default principal.

Note that this was all working before the upgrade. The upgrade was
2022-01-10  15:09:15

Looks like the system was installed July 31, 2020, and no upgrades other
than unattended upgrade since then.

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

Title:
  nfs v3 locking fails - rpc-statd not started after minor upgrade

Status in nfs-utils package in Ubuntu:
  Incomplete

Bug description:
  We just upgraded our nfs servers from 5.4.0-72 to 5.4.0-92.

  We are using NFS v3 in a large computer science department, with
  several hundred clients.

  Lots of applications are now failing because locks don't work.

  /var/log/syslog on the client reports lockd not responding. tcpdump
  shows that the client tries to connect to lockd but there is no
  response to the TCP SYN.

  netstat on the server shows some connections open, with lots of bytes
  in the receive queue.

  The problem probably occurs only with lots of clients. I believe any
  typical test would work fine.

  The problem is new. That is, it didn't happen in 5.4.0-72.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Uname: Linux 5.4.0-92-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Jan  7 13:07:34 2022
  InstallationDate: Installed on 2020-10-14 (450 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-10-14T13:53:33.474467

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