RPC error 111

RPC error 111

[jim roy]

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 

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?

Thanks,

Jim Roy
*************************************************************************
Northwest Geophysical Associates, Inc.                 http://www.nga.com
Box 1063
Corvallis, Oregon 97339                                
voice: 541-757-7231 / fax 541-757-7331 

Re: RPC error 111

[Glynn Clements]

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>

Re: RPC error 111 (solved)

[jim roy]

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