Activity log for bug #1689777

Date Who What changed Old value New value Message
2017-05-10 09:45:18 Alexander bug added bug
2017-05-10 10:00:10 Brad Figg linux (Ubuntu): status New Incomplete
2017-05-10 10:00:12 Brad Figg tags trusty
2017-05-10 10:18:55 Alexander attachment added syslog https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689777/+attachment/4874563/+files/syslog
2017-05-10 10:19:25 Alexander attachment removed syslog https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689777/+attachment/4874563/+files/syslog
2017-05-10 10:20:13 Alexander attachment added syslog https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689777/+attachment/4874565/+files/syslog
2017-05-10 10:20:22 Alexander linux (Ubuntu): status Incomplete Confirmed
2017-05-11 20:15:27 Alexander linux (Ubuntu): status Confirmed Opinion
2017-05-11 20:40:24 Alexander linux (Ubuntu): status Opinion Invalid
2017-05-11 21:23:01 Alexander affects linux (Ubuntu) nfs-utils (Ubuntu)
2017-05-11 21:23:01 Alexander nfs-utils (Ubuntu): status Invalid New
2017-05-11 21:28:02 Alexander summary NFS lockd error NFS lockd error cannot monitor client
2017-05-11 22:03:25 Alexander 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 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. Following log is produced on a client that mounts nfs: May 10 00:46:23 irminen kernel: [2972685.514114] lockd: server pranger.uni-trier.de OK May 10 00:47:24 irminen kernel: [2972746.611297] lockd: server pranger.uni-trier.de 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. 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 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. 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.
2017-05-12 09:28:21 Alexander 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 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. 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. 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)
2017-05-12 09:28:46 Alexander attachment added aptHistory.log https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1689777/+attachment/4875513/+files/aptHistory.log
2017-07-18 18:20:26 Launchpad Janitor nfs-utils (Ubuntu): status New Confirmed
2017-07-18 18:21:18 Brant Gardner bug added subscriber Brant Gardner