Red Hat Bugzilla – Bug 78004
NFS: lockd can't monitor client / client can't lock files
Last modified: 2007-04-18 12:48:30 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
If a nfs-client tries to lock a file on the nfs-server, the server reports
"lockd: cannot monitor <client-ip>" directly to the console without producing
Some applications on the client (like gnome-volume-control) report the unability
to lock files and continue, others (esp. gnome2) report it and abort.
This bug occurs since i've updated the client from RedHat Linux 7.3 (which
worked well) to RedHat Linux 8.0.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mount /home from nfs-server (server: RedHat Linux 7.3, client: RedHat Linux 8.0)
2. start gnome2 (as none-root)
Actual Results: Errormessage: "Can't lock %gconf-xml-backend.lock. Aborting"
Expected Results: Nothing, just a started gnome2
Both systems (server and client) are kept up-to-date with all errata installed.
Kernel on server: 2.4.18-17.7.x
Kernel on client: 2.4.18-17.8.0
nfs-utils on both systems: 1.0.1-2
Are there any log messages produced on the client? Check your firewall setup on
the client to make sure that the server's statd requests are not being blocked.
First message is from gnome2 (while starting gnome2) that
~/.gnome-locking-test-file (or so) could not be locked. It says I should check
my nfslock service, which is running.
/var/log/messages states that a session was opened and closed.
There is no firewall on the client and the firewall on the server is configured
to pass any packets on the interface in question.
Please reopen if the problem persists with a current release.