NFS error: "lockd: cannot monitor client"

English Network/Internet
#1

Hi!

Opensuse 13-1_x86_64. NFS server running.

Ubuntu clients identified by NIS and mount /home using auto home
When a client enter the system in console he mounts his home OK, and there is no error. Using ice-WM it woks fine too. But there is some scenarios in which I get a lot of errors:

1st one: in ice-wm I open firefox, then I get a dozen of errors


2016-02-01T08:46:12.906562+01:00 tutatis kernel: [519098.525183] lockd: cannot monitor pc1411
2016-02-01T08:46:12.922603+01:00 tutatis kernel: [519098.538314] lockd: cannot monitor pc1411
2016-02-01T08:46:12.922635+01:00 tutatis kernel: [519098.541265] lockd: cannot monitor pc1411
2016-02-01T08:46:12.938582+01:00 tutatis kernel: [519098.554890] lockd: cannot monitor pc1411
2016-02-01T08:46:13.266630+01:00 tutatis kernel: [519098.884246] lockd: cannot monitor pc1411
2016-02-01T08:46:14.786589+01:00 tutatis kernel: [519100.403282] lockd: cannot monitor pc1411
2016-02-01T08:46:14.798618+01:00 tutatis kernel: [519100.418113] lockd: cannot monitor pc1411
2016-02-01T08:46:14.838573+01:00 tutatis kernel: [519100.455195] lockd: cannot monitor pc1411
2016-02-01T08:46:14.838603+01:00 tutatis kernel: [519100.456543] lockd: cannot monitor pc1411
2016-02-01T08:46:14.838606+01:00 tutatis kernel: [519100.457814] lockd: cannot monitor pc1411
2016-02-01T08:46:14.842573+01:00 tutatis kernel: [519100.459365] lockd: cannot monitor pc1411
2016-02-01T08:46:14.910582+01:00 tutatis kernel: [519100.530177] lockd: cannot monitor pc1411

If i use KDE instead ice-wm, then i get hundreds of errors (same errors)


root@tutatis:/home/fperal> cat /etc/exports
/home   192.168.2.0/255.255.255.0(crossmnt,rw,root_squash,async,no_subtree_check)
/imagenes       192.168.2.*(rw,sync,no_subtree_check)

The clients are mounting using nfsv3.

The configuration of NFS server in yast is quite straightforward and it seems to work except that errors, but it makes KDE on the clients unusable.

What should i look for?

regards

#2

Could it be the “async” option?

#3

No. I’ve tried with sync, same problem.

regards

#4

So did you ever resolve your problem? If so, how? I am now facing this exact same thing in Ubuntu 16.04. In an older version, things worked fine, I had my /home on nfsv3. In new Ubuntu version, if I log in via ssh and work with only few files at a time, things work fine. If I log into GUI, the server starts spitting out lockd: cannot monitor name_of_my_computer. And on the client computer, I get extremely slow gui startup (10 minutes) and/or complaints that nfs server is unreachable.

This thread reminds me of: https://xkcd.com/979/