SM_UNMON again -> kernel

[Lawrence Ong <lawrence.ong@netregistry.com.au>]

Hi Everybody,

If someone can shed some light on why this annoying message kept
appearing, it would be much appreciated.  I'm sure a lot of other
people out there are getting the same error message.

The Error in Syslog that we continually get is the common:

Received erroneous SM_UNMON request from mymachine for 10.1.1.20

The error does not break NFS or anything.  It's just a rather annoying
message that kept on appearing again and again.  Looking through the
different mailing list did not help.  None of the solutions provided
refers to kernel 2.4.19-21 or is the reason why it gives that error.

SYSTEM INFORMATION
------------------
The system that we're using is booting off the kernel 2.4.21 kernel with
nfs-utils 1.0.3 on a Debian Woody system.  We have also tested this on
2.4.19 and 2.4.20 with and without Trond's NFS (FIXES/ALL) patches.  We
have also tested the system with nfs-utils version 1.0.0.

We noticed that it is getting that error because in monitor.c, the
value generated by NL_MY_NAME(clnt) is 127.0.0.1?  Is this suppose to be
correct?!

The NFS server contains the IP address 10.1.1.20, mymachine is the client
with the IP address 10.1.1.180.  The client mounts the server as such:

10.1.1.20:/mountpath /mountpath nfs rsize=8192,wsize=8192,nfsvers=3,udp,noatime,hard,intr,bg 0 0

STEPPING THROUGH CODE
---------------------
Looking at utils/statd/monitor.c - we have lines that read:

--------------
while ((clnt = nlist_gethost(clnt, mon_name, 0))) {
	if (matchhostname(NL_MY_NAME(clnt), my_name) &&
--------------

This matchhostname never match because NL_MY_NAME(clnt) gives 127.0.0.1
but the my_name variable in sm_unmon_1_svc function is mymachine.

THEN LOOKING AT FURTHER CODE
----------------------------

In monitor.c again, in the sm_mon_1_svc function, we have:

struct sm_stat_res *
sm_mon_1_svc(struct mon *argp, struct svc_req *rqstp)
{
        static sm_stat_res result;
        char            *mon_name = argp->mon_id.mon_name,
                        *my_name  = argp->mon_id.my_id.my_name;
...
my_name = "127.0.0.1";

What the?!  my_name is reset to 127.0.0.1 due to some CERT Advisory
CA-99.05?  Anyhow, lets just ignore that since this is not the main
cause of why the error message appears in the first place.  Now we're
back to the kernel that kept on producing an SM_UNMON RPC to statd.

It looks like this unmon stufff is happening too regularly?  Now i'm
wondering why it is attempting to UNMON so regularly in the first place?

This brings us back to kernel 2.4.19-21.  Why is the kernel's statd client
calling statd so regularly for sm_unmon?!!!  No, i did not stop the
nfs-kernel-server.  No, i'm not mounting and unmounting NFS regularly.

Is there something else i should check?  I'll start looking at the kernel
code while awaiting reply.  Any help/suggestions appreciated.

Cheers,
Lawrence


-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs