All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diego Moreno <Diego.Moreno-Lazaro@bull.net>
To: linux-nfs@vger.kernel.org
Subject: rpc.statd problem: lockd: cannot monitor server
Date: Tue, 01 Dec 2009 18:14:15 +0100	[thread overview]
Message-ID: <4B154EE7.8050700@bull.net> (raw)

Hi guys,

We are having a problem with locks in NFSv3 with Fedora11. I've been 
searching this problem in the list for a while but I haven't found it.

The problem is in Fedora11, kernel 2.6.29.6-217.2.16.fc11 and 
nfs-utils-1.1.5-6.fc11

When I try to make two locks with two different process I get the 
message "No locks available". rpc.statd is running on client and server, 
also lockd. If I try with just one process I obtain the same result.

I tried to debug with wireshark and I can see client is not trying to 
make a lock. I also tried to enable NLM debug and I get next messages:

Syslog:

1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: get 
host myserver
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: get 
host myserver
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: 
nsm_monitor(myserver)
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: get 
host myserver
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: get 
host myserver
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: 
nsm_monitor(myserver)
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: 
xdr_dec_stat_res status 1 state -1
1259574201 2009 Nov 30 10:43:21 myclient kern notice kernel lockd: 
cannot monitor myserver
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: 
release host myserver
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: 
release host myserver
1259574201 2009 Nov 30 10:43:21 myclient daemon warning rpc.statd 
creat(/var/lib/nfs/statd/sm/myserver) failed: No such file or directory
1259574201 2009 Nov 30 10:43:21 myclient daemon notice rpc.statd 
STAT_FAIL to myclient for SM_MON of 10.0.4.60
1259574201 2009 Nov 30 10:43:21 myclient daemon warning rpc.statd 
creat(/var/lib/nfs/statd/sm/myserver) failed: No such file or directory
1259574201 2009 Nov 30 10:43:21 myclient daemon notice rpc.statd 
STAT_FAIL to myclient for SM_MON of 10.0.4.60
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: clnt 
proc returns -37
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: 
xdr_dec_stat_res status 1 state -1
1259574201 2009 Nov 30 10:43:21 myclient kern notice kernel lockd: 
cannot monitor myserver
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: 
release host myserver
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: 
release host myserver
1259574201 2009 Nov 30 10:43:21 myclient kern warning kernel lockd: clnt 
proc returns -37

It's like if rpc.statd was not running, but it is. Should ../statd/sm/ 
directory be already created when we try the lock?

Is this a known problem?

Thanks,

             reply	other threads:[~2009-12-01 17:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 17:14 Diego Moreno [this message]
2009-12-01 17:34 ` rpc.statd problem: lockd: cannot monitor server Chuck Lever
2009-12-02 10:22   ` Diego Moreno
2009-12-02 12:29     ` Jeff Layton
     [not found]       ` <20091202072928.14b9399c-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-12-03 10:24         ` Diego Moreno
2009-12-03 12:20           ` Jeff Layton
     [not found]             ` <20091203072030.0a2f029a-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>
2009-12-07 14:52               ` Diego Moreno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B154EE7.8050700@bull.net \
    --to=diego.moreno-lazaro@bull.net \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.