lockd trouble

lockd trouble

[Jussi Hamalainen]

I have two PCs running Slackware 7.1. I can't get lockd to work
properly with NFS:

Apr 10 21:03:59 sputnik kernel: nsm_mon_unmon: rpc failed, status=-93
Apr 10 21:03:59 sputnik kernel: lockd: cannot monitor xxx.xxx.xxx.xxx
Apr 10 21:03:59 sputnik kernel: lockd: failed to monitor xxx.xxx.xxx.xxx

Yet rpcinfo -p gives the following:

magellan:~$ rpcinfo -p mir
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100021    1   udp   1024  nlockmgr
    100021    3   udp   1024  nlockmgr
    100005    1   udp    686  mountd
    100005    2   udp    686  mountd
    100005    1   tcp    689  mountd
    100005    2   tcp    689  mountd
    100003    2   udp   2049  nfs
    100003    2   tcp   2049  nfs
magellan:~$ rpcinfo -p sputnik
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100021    1   udp   1024  nlockmgr
    100021    3   udp   1024  nlockmgr
    100005    1   udp    721  mountd
    100005    2   udp    721  mountd
    100005    1   tcp    724  mountd
    100005    2   tcp    724  mountd
    100003    2   udp   2049  nfs
    100003    2   tcp   2049  nfs

The NFS share in question is mounted as locking. Every time procmail
tries to get a kernel lock for a file in my home directory, I get an
error as described above. Both boxes are running exactly the same
2.2.19 kernel. Am I doing something wrong or is this a bug?

-- 
-=[ Count Zero / TBH - Jussi Hämäläinen - email count@theblah.org ]=-

Re: lockd trouble

[Jussi Hamalainen]

On Tue, 10 Apr 2001, Jussi Hamalainen wrote:

>    program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     100021    1   udp   1024  nlockmgr
>     100021    3   udp   1024  nlockmgr
>     100005    1   udp    686  mountd
>     100005    2   udp    686  mountd
>     100005    1   tcp    689  mountd
>     100005    2   tcp    689  mountd
>     100003    2   udp   2049  nfs
>     100003    2   tcp   2049  nfs

Duhh. Obviously I should have read the documentation before bashing
my head against the wall. I wasn't running statd. Got it working now,
sorry about that.

I do have a question about lockd. How do I get it back if I need
to restart portmap? Running rpc.lockd doesn't seem to have any
effect whatsoever on the listed rpc services and I can't just
reload the module since nfs depends on it.

-- 
-=[ Count Zero / TBH - Jussi Hämäläinen - email count@theblah.org ]=-

Re: lockd trouble

[Trond Myklebust]

>>>>> " " == Jussi Hamalainen <count@theblah.org> writes:

     > I do have a question about lockd. How do I get it back if I
     > need to restart portmap? Running rpc.lockd doesn't seem to have
     > any effect whatsoever on the listed rpc services and I can't
     > just reload the module since nfs depends on it.

You can use pmap_dump/pmap_set to save/restore the
state. Alternatively umount all NFS partitions, and stop all nfsd
servers: lockd will unregister itself when it sees that it is no
longer needed.

Cheers,
  Trond