Skip to contentSkip to conversation

rpc.statd problem: lockd: cannot monitor server

DISCUSSION Diego Moreno 3 participants 7 messages Dec 1, 2009 – Dec 7, 2009 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore 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,

#1 lore raw
Quoted 12 lines · Diego Moreno

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:

Quoted 13 lines

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

Statd can't create the monitor record for this remote peer for some reason. Check that /var/lib/nfs/statd and /var/lib/nfs/statd/sm exist, and are permitted so that rpc.statd can create files in it. Check which uid and gid statd is running under: I think F11 uses 29 for both.

Quoted 17 lines

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,
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 2 lines
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
#2 lore raw
Quoted 27 lines · Chuck Lever
Quoted 12 lines · Diego Moreno

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:

Quoted 13 lines

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

Quoted 2 lines

Statd can't create the monitor record for this remote peer for some reason. Check that /var/lib/nfs/statd and /var/lib/nfs/statd/sm exist, and are permitted so that rpc.statd can create files in it. Check which uid and gid statd is running under: I think F11 uses 29 for both.

Thanks Chuck. That made the trick. Directory /var/lib/nfs/statd/ was empty in client and server. Adding these directories locking works. But it's just a workaround as I have 30 more clients having the same problem. I'm going to try to find out why this is happening. Maybe it is a bug in fedora installation? When are supposed the files under "/var/lib/nfs/statd/" to be created?

statd is running under the right uid and gid and /var/lib/nfs/statd is owned by rpcuser as it should be.

Quoted 18 lines
Quoted 17 lines

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,

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw
Quoted 62 lines · On Wed, 02 Dec 2009 11:22:49 +0100 Diego Moreno <[email protected]>…
Quoted 46 lines · Chuck Lever
Quoted 36 lines · Diego Moreno

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

Quoted 8 lines

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

Quoted 5 lines

Statd can't create the monitor record for this remote peer for some reason. Check that /var/lib/nfs/statd and /var/lib/nfs/statd/sm exist, and are permitted so that rpc.statd can create files in it. Check which uid and gid statd is running under: I think F11 uses 29 for both.

Thanks Chuck. That made the trick. Directory /var/lib/nfs/statd/ was empty in client and server. Adding these directories locking works. But it's just a workaround as I have 30 more clients having the same problem. I'm going to try to find out why this is happening. Maybe it is a bug in fedora installation? When are supposed the files under "/var/lib/nfs/statd/" to be created?

Quoted 3 lines

statd is running under the right uid and gid and /var/lib/nfs/statd is owned by rpcuser as it should be.

Sounds like a packaging bug, but when I look at CVS for that nfs-utils version it looks ok:

%files

[...]

%dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd %dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd/sm %dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd/sm.bak

...if you uninstall and reinstall the nfs-utils package on one of these hosts, do these directories get put in place correctly?

Signature · 1 line
Jeff Layton <[email protected]>

A message that is not in the archive (sent off-list or not yet received): 20091202072928.14b9399c-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org

#5 lore raw
Quoted 43 lines · Jeff Layton
Quoted 28 lines · On Wed, 02 Dec 2009 11:22:49 +0100 Diego Moreno <[email protected]>…
Quoted 26 lines · Chuck Lever
Quoted 25 lines · Diego Moreno

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

Quoted 6 lines
Quoted 2 lines

Statd can't create the monitor record for this remote peer for some reason. Check that /var/lib/nfs/statd and /var/lib/nfs/statd/sm exist, and are permitted so that rpc.statd can create files in it. Check which uid and gid statd is running under: I think F11 uses 29 for both.

Thanks Chuck. That made the trick. Directory /var/lib/nfs/statd/ was empty in client and server. Adding these directories locking works. But it's just a workaround as I have 30 more clients having the same problem. I'm going to try to find out why this is happening. Maybe it is a bug in fedora installation? When are supposed the files under "/var/lib/nfs/statd/" to be created?

statd is running under the right uid and gid and /var/lib/nfs/statd is owned by rpcuser as it should be.

Sounds like a packaging bug, but when I look at CVS for that nfs-utils version it looks ok:

%files

Quoted 9 lines

[...]

%dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd %dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd/sm %dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd/sm.bak

...if you uninstall and reinstall the nfs-utils package on one of these hosts, do these directories get put in place correctly?

That's right Jeff. Uninstalling and reinstalling nfs-utils everything worked fine and now statd files are there with locks working as they should.

Thanks!

#6 lore raw
Quoted 80 lines · On Thu, 03 Dec 2009 11:24:42 +0100 Diego Moreno <[email protected]>…
Quoted 77 lines · Jeff Layton
Quoted 59 lines · On Wed, 02 Dec 2009 11:22:49 +0100 Diego Moreno <[email protected]>…
Quoted 45 lines · Chuck Lever
Quoted 36 lines · Diego Moreno

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

Quoted 8 lines

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

Quoted 5 lines

Statd can't create the monitor record for this remote peer for some reason. Check that /var/lib/nfs/statd and /var/lib/nfs/statd/sm exist, and are permitted so that rpc.statd can create files in it. Check which uid and gid statd is running under: I think F11 uses 29 for both.

Thanks Chuck. That made the trick. Directory /var/lib/nfs/statd/ was empty in client and server. Adding these directories locking works. But it's just a workaround as I have 30 more clients having the same problem. I'm going to try to find out why this is happening. Maybe it is a bug in fedora installation? When are supposed the files under "/var/lib/nfs/statd/" to be created?

Quoted 3 lines

statd is running under the right uid and gid and /var/lib/nfs/statd is owned by rpcuser as it should be.

Sounds like a packaging bug, but when I look at CVS for that nfs-utils version it looks ok:

%files

[...]

%dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd %dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd/sm %dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd/sm.bak

Quoted 9 lines
Quoted 3 lines

...if you uninstall and reinstall the nfs-utils package on one of these hosts, do these directories get put in place correctly?

That's right Jeff. Uninstalling and reinstalling nfs-utils everything worked fine and now statd files are there with locks working as they should.

Thanks!

Strange. Were these machines fresh installs, or were they upgrades from an earlier fedora release?

Signature · 1 line
Jeff Layton <[email protected]>

A message that is not in the archive (sent off-list or not yet received): 20091203072030.0a2f029a-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org

#8 lore raw
Quoted 55 lines · Jeff Layton
Quoted 52 lines · On Thu, 03 Dec 2009 11:24:42 +0100 Diego Moreno <[email protected]>…
Quoted 50 lines · Jeff Layton
Quoted 27 lines · On Wed, 02 Dec 2009 11:22:49 +0100 Diego Moreno <[email protected]>…
Quoted 26 lines · Chuck Lever
Quoted 25 lines · Diego Moreno

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

Quoted 6 lines
Quoted 2 lines

Statd can't create the monitor record for this remote peer for some reason. Check that /var/lib/nfs/statd and /var/lib/nfs/statd/sm exist, and are permitted so that rpc.statd can create files in it. Check which uid and gid statd is running under: I think F11 uses 29 for both.

Thanks Chuck. That made the trick. Directory /var/lib/nfs/statd/ was empty in client and server. Adding these directories locking works. But it's just a workaround as I have 30 more clients having the same problem. I'm going to try to find out why this is happening. Maybe it is a bug in fedora installation? When are supposed the files under "/var/lib/nfs/statd/" to be created?

statd is running under the right uid and gid and /var/lib/nfs/statd is owned by rpcuser as it should be.

Sounds like a packaging bug, but when I look at CVS for that nfs-utils version it looks ok:

%files

[...]

%dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd %dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd/sm %dir %attr(700,rpcuser,rpcuser) /var/lib/nfs/statd/sm.bak

...if you uninstall and reinstall the nfs-utils package on one of these hosts, do these directories get put in place correctly?

Quoted 8 lines
Quoted 4 lines

That's right Jeff. Uninstalling and reinstalling nfs-utils everything worked fine and now statd files are there with locks working as they should.

Thanks!

Strange. Were these machines fresh installs, or were they upgrades from an earlier fedora release?

Now we know why we had this problem. The problem comes from a system management tool we're developing. We made system snapshots for installation and we were not copying statd directory. This solution worked (well?) with Red Hat 5.3 as if there is no statd directory it's created when a lock is required (but under root user, not 'rpcuser'). But with Fedora 11 this directory is not created again.

- Which is the good behavior (if there's any good behavior...)?