All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Troin <phil@fifi.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Lawrence Ong <lawrence.ong@netregistry.com.au>,
	nfs@lists.sourceforge.net
Subject: Re: SM_UNMON again -> kernel
Date: 13 Jul 2003 11:00:03 -0700	[thread overview]
Message-ID: <87k7aml330.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <shs8yr2h2jr.fsf@charged.uio.no>

Trond Myklebust <trond.myklebust@fys.uio.no> writes:

> >>>>> " " == Philippe Troin <phil@fifi.org> writes:
> 
>      > Trond Myklebust <trond.myklebust@fys.uio.no> writes:
>     >> Is /etc/hosts consistent? The kernel only sends MON/UNMON
>     >> requests on the loopback port, so this suggests that something
>     >> is translating 127.0.0.1<->"mymachine" instead of to
>     >> "localhost".
> 
>      > I've also been seeing this forever... Which also means that
>      > locks are never recovered after a server reboot, which is midly
>      > annoying.
> 
> The *same* error, with a message that appears not to be originating
> from 127.0.0.l?

Yup.

On machine #1:
ceramic rpc.statd[30693]: Received erroneous SM_UNMON request from ceramic for 216.27.190.149

On machine #2:
tantale rpc.statd[18416]: Received erroneous SM_UNMON request from tantale for 216.27.190.148

>      > What do you mean by "consistent" /etc/hosts?
> 
> I mean crap like
> 
> 127.0.0.l     localhost mymachine
> 
> in /etc/hosts, together with a DNS entry translates the name
> "mymachine" into another IP address.
> 
> Believe me. It's been done...

Oh, I'm sure about that :-)

Phil.


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

  reply	other threads:[~2003-07-13 18:00 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 [this message]
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:
  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=87k7aml330.fsf@ceramic.fifi.org \
    --to=phil@fifi.org \
    --cc=lawrence.ong@netregistry.com.au \
    --cc=nfs@lists.sourceforge.net \
    --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.