Bug 78004
Summary: | NFS: lockd can't monitor client / client can't lock files | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Felix Tiede <tiede> |
Component: | nfs-utils | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED WORKSFORME | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | crn1 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i586 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-03-10 16:48:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Felix Tiede
2002-11-17 09:09:07 UTC
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. |