[Bug 1689777] Re: NFS lockd error cannot monitor client

[Alexander]

Added APT history of updated packages

** Description changed:

  System:
  Description:	Ubuntu 14.04.5 LTS
  Release:	14.04
  Version signature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59
+ Using NFS-common and NFS-kernel-server version 1:1.2.8-6ubuntu1.2 before kernel update and after.
  
- Using NFS-common and NFS-kernel-server version 1:1.2.8-6ubuntu1.2 before
- kernel update and after.
  
- After an update from linux-image-generic-lts-xenial:amd64 4.4.0.64.50 to version 4.4.0.75.62, our NFS server refuses any exclusive file locks after every night. Symptoms are that NFS clients cannot execute programs that use exclusive file locks (e.g. cradle), if using a UI like Ubuntu Desktop, the whole UI is stuck. However files can still be accessed and created via shell on a client through nfs.
+ After an update of a few packages (list attached), our NFS server refuses exclusive file locks after about 24h of runtime. Symptoms are that NFS clients cannot execute programs that use exclusive file locks (e.g. gradle), if using a UI like Ubuntu Desktop, the whole UI is stuck. However files can still be accessed and created via shell on a client through nfs.
  Following log is produced on a client that mounts nfs:
  
  May 10 00:46:23 irminen kernel: [2972685.514114] lockd: server pranger OK
  May 10 00:47:24 irminen kernel: [2972746.611297] lockd: server pranger not responding, still trying
  
  The nfs server produces following log:
  
  May  8 22:30:22 pranger kernel: [6267842.076551] Btrfs loaded
  May  9 04:16:02 pranger kernel: [6288582.711415] lockd: cannot monitor client
  May  9 04:17:02 pranger kernel: [6288642.871345] lockd: cannot monitor client
  May  9 04:18:03 pranger kernel: [6288703.031317] lockd: cannot monitor client
  May  9 04:19:03 pranger kernel: [6288763.191282] lockd: cannot monitor client
  May  9 04:20:03 pranger kernel: [6288823.351247] lockd: cannot monitor client
  May  9 04:21:03 pranger kernel: [6288883.511292] lockd: cannot monitor client
  May  9 04:22:03 pranger kernel: [6288943.671215] lockd: cannot monitor client
  May  9 04:23:03 pranger kernel: [6289003.831189] lockd: cannot monitor client
  
  Restarting the NFS Server does not resolve the issue, I had to reboot
  the server completely. After one day running the same problem appears
  again.
+ 
+ Mounted on 14.04 and 16.04 machines via
+ pranger:/srv/home /home			nfs	nfsvers=3	0
+ 
+ More info in Comment #7 (https://bugs.launchpad.net/ubuntu/+source/nfs-
+ utils/+bug/1689777/comments/7)

** Attachment added: "aptHistory.log"
   https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1689777/+attachment/4875513/+files/aptHistory.log

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

Title:
  NFS lockd error cannot monitor client

Status in nfs-utils package in Ubuntu:
  New

Bug description:
  System:
  Description:	Ubuntu 14.04.5 LTS
  Release:	14.04
  Version signature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59
  Using NFS-common and NFS-kernel-server version 1:1.2.8-6ubuntu1.2 before kernel update and after.

  
  After an update of a few packages (list attached), our NFS server refuses exclusive file locks after about 24h of runtime. Symptoms are that NFS clients cannot execute programs that use exclusive file locks (e.g. gradle), if using a UI like Ubuntu Desktop, the whole UI is stuck. However files can still be accessed and created via shell on a client through nfs.
  Following log is produced on a client that mounts nfs:

  May 10 00:46:23 irminen kernel: [2972685.514114] lockd: server pranger OK
  May 10 00:47:24 irminen kernel: [2972746.611297] lockd: server pranger not responding, still trying

  The nfs server produces following log:

  May  8 22:30:22 pranger kernel: [6267842.076551] Btrfs loaded
  May  9 04:16:02 pranger kernel: [6288582.711415] lockd: cannot monitor client
  May  9 04:17:02 pranger kernel: [6288642.871345] lockd: cannot monitor client
  May  9 04:18:03 pranger kernel: [6288703.031317] lockd: cannot monitor client
  May  9 04:19:03 pranger kernel: [6288763.191282] lockd: cannot monitor client
  May  9 04:20:03 pranger kernel: [6288823.351247] lockd: cannot monitor client
  May  9 04:21:03 pranger kernel: [6288883.511292] lockd: cannot monitor client
  May  9 04:22:03 pranger kernel: [6288943.671215] lockd: cannot monitor client
  May  9 04:23:03 pranger kernel: [6289003.831189] lockd: cannot monitor client

  Restarting the NFS Server does not resolve the issue, I had to reboot
  the server completely. After one day running the same problem appears
  again.

  Mounted on 14.04 and 16.04 machines via
  pranger:/srv/home /home			nfs	nfsvers=3	0

  More info in Comment #7 (https://bugs.launchpad.net/ubuntu/+source
  /nfs-utils/+bug/1689777/comments/7)

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