All of
 help / color / mirror / Atom feed
From: Lawrence Ong <>
Subject: SM_UNMON again -> kernel
Date: Fri, 11 Jul 2003 16:16:15 +1000	[thread overview]
Message-ID: <> (raw)

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

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.

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  Is this suppose to be

The NFS server contains the IP address, mymachine is the client
with the IP address  The client mounts the server as such: /mountpath nfs rsize=8192,wsize=8192,nfsvers=3,udp,noatime,hard,intr,bg 0 0

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
but the my_name variable in sm_unmon_1_svc function is mymachine.


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 = "";

What the?!  my_name is reset to 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.


This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
NFS maillist  -

             reply	other threads:[~2003-07-11  6:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11  6:16 Lawrence Ong [this message]
2003-07-11  9:38 ` SM_UNMON again -> kernel Trond Myklebust
2003-07-13  3:22   ` Philippe Troin
2003-07-13 15:25     ` Trond Myklebust
2003-07-13 18:00       ` Philippe Troin
2003-07-13 23:36         ` Lawrence Ong
2003-07-14  8:56         ` Trond Myklebust
2003-07-18  1:08           ` Philippe Troin
2003-07-19  3:26             ` Philippe Troin
2003-07-19 16:22               ` Christian Reis
2003-07-20 23:28                 ` Trond Myklebust
2003-07-20 23:45                   ` Christian Reis
2003-07-21 13:08                     ` Bogdan Costescu
2003-07-13  4:25   ` Lawrence Ong
2003-07-14  8:47     ` Trond Myklebust
2003-07-14 23:42       ` Lawrence Ong

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:

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

  git send-email \ \ \ \

* 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.