All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glynn Clements <glynn.clements@virgin.net>
To: jim roy <jim@nga.com>
Cc: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: RPC error 111
Date: Wed, 23 Jul 2003 23:25:44 +0100	[thread overview]
Message-ID: <16159.2920.555315.263533@cerise.nosuchdomain.co.uk> (raw)
In-Reply-To: <20030723102012.M13062@redwing>


jim roy wrote:

> What are these kernel log entries trying to tell me?
> 
> Jul 22 10:02:49 marty kernel: nfs: RPC call returned error 111 
> Jul 22 10:02:49 marty kernel: RPC: task of released request still queued! 
> Jul 22 10:02:49 marty kernel: RPC: (task is on xprt_pending) 
> Jul 22 10:02:49 marty kernel: nfs_revalidate_inode: /// getattr failed, ino=1879048194, error=-111 

Error 111 is ECONNREFUSED, which implies that the NFS server is
refusing connections.

> This is on an old reliable file server that has been doing it's thing
> for months.  2.2 kernel.  Over the last few days, this has begun to crop up.
> Several windows machines have been moving on & off the network lately, could
> this be a samba problem?

It isn't related to SMB. Could one of the Windows boxes have stolen
the NFS server's IP address?

If you have problems with IP address conflicts, running arpwatch could
help.

-- 
Glynn Clements <glynn.clements@virgin.net>

  reply	other threads:[~2003-07-23 22:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 17:20 RPC error 111 jim roy
2003-07-23 22:25 ` Glynn Clements [this message]
2003-07-24 19:21   ` RPC error 111 (solved) jim roy

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=16159.2920.555315.263533@cerise.nosuchdomain.co.uk \
    --to=glynn.clements@virgin.net \
    --cc=jim@nga.com \
    --cc=linux-admin@vger.kernel.org \
    /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.