From: Christian Reis <kiko@async.com.br>
To: Philippe Troin <phil@fifi.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: SM_UNMON again -> kernel
Date: Sat, 19 Jul 2003 13:22:18 -0300 [thread overview]
Message-ID: <20030719162218.GB7166@async.com.br> (raw)
In-Reply-To: <87n0fb42o5.fsf@ceramic.fifi.org>
On Fri, Jul 18, 2003 at 08:26:50PM -0700, Philippe Troin wrote:
> I still see the same messages over and over again.
Just to add a data point, I see the same message periodically on our
diskless network -- all clients are linux 2.4.21 (debian woody), as is
the server (no relevant patches). However, the IP addresses in the
messages are for the *remote* boxes.
Server (anthem 192.168.99.4) logs:
Jul 12 17:50:10 anthem rpc.statd[326]: Received erroneous
SM_UNMON request from anthem for 192.168.99.6
Jul 12 17:54:37 anthem rpc.statd[326]: Received erroneous
SM_UNMON request from anthem for 192.168.99.6
Jul 12 18:07:03 anthem rpc.statd[326]: Received erroneous
SM_UNMON request from anthem for 192.168.99.6
Jul 12 18:13:10 anthem rpc.statd[326]: Received erroneous
SM_UNMON request from anthem for 192.168.99.6
[One] client (manonegra 192.168.99.6) log:
Jul 18 18:07:33 manonegra rpc.statd[115]: Received
erroneous SM_UNMON request from manonegra for 192.168.99.4
Jul 18 18:17:33 manonegra rpc.statd[115]: Received
erroneous SM_UNMON request from manonegra for 192.168.99.4
Jul 18 18:35:08 manonegra rpc.statd[115]: Received
erroneous SM_UNMON request from manonegra for 192.168.99.4
Jul 18 18:39:22 manonegra rpc.statd[115]: Received
erroneous SM_UNMON request from manonegra for 192.168.99.4
It goes on forever. There's nothing fishy on the 127.0.0.1 lines in the
hosts file or in DNS. The logs go back for a year now.
If there's one thing special, it's that this server also runs an
iptables firewall that does masquerading and supports connection
tracking. Could it be mangling the lock packets? I recall seeing
something similar a long time ago..
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-07-19 16:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 6:16 SM_UNMON again -> kernel Lawrence Ong
2003-07-11 9:38 ` 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 [this message]
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:
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=20030719162218.GB7166@async.com.br \
--to=kiko@async.com.br \
--cc=nfs@lists.sourceforge.net \
--cc=phil@fifi.org \
--cc=trond.myklebust@fys.uio.no \
/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.