From: jim roy <jim@nga.com>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: RPC error 111 (solved)
Date: Thu, 24 Jul 2003 12:21:52 -0700 [thread overview]
Message-ID: <20030724122152.U13062@redwing> (raw)
In-Reply-To: <16159.2920.555315.263533@cerise.nosuchdomain.co.uk>; from glynn.clements@virgin.net on Wed, Jul 23, 2003 at 15:25:44 -0700
In trying to figure this out, I saw lots of similar questions out there,
but few answers, so maybe this will help some other poor soul.
Glen, as usual, was right on the mark. But it wasn't this system ( marty )
that had the problem. The NFS server on another machine was not responding.
A system monitoring script on marty runs the df command, and logs this error
when it trys to stat the other machine's exported fs.
On 2003.07.23 15:25 Glynn Clements wrote:
>
> 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>
>
prev parent reply other threads:[~2003-07-24 19:21 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
2003-07-24 19:21 ` jim roy [this message]
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=20030724122152.U13062@redwing \
--to=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.