Re: Debian Bug#203077: Locks not released on NFS client reboot

[Dan Stromberg <strombrg@dcs.nac.uci.edu>]

[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]

On Fri, 2005-01-14 at 13:29 +1100, Neil Brown wrote:
> On Thursday January 13, Ara.T.Howard@noaa.gov wrote:
> > 
> > i am seeing problems here on my system (which has rebooted and now has stale
> > locks on server)
> > 
> ..
> >    server:
> > 
> >      mussel:~ > rpcinfo -u bligh status
> >      rpcinfo: RPC: Port mapper failure - RPC: Unable to receive
> >      program 100024 is not available
> ...
> > 
> >    client:
> > 
> >      bligh:~ > rpcinfo -p
> >         program vers proto   port
> >          100000    2   tcp    111  portmapper
> >          100000    2   udp    111  portmapper
> >          100024    1   udp  32768  status
> >          100024    1   tcp  32768  status
> ...
> 
> 
> So bligh, the client, is running statd (the "status" service), but
> mussel can not talk to it.  This is a problem.
> 
> It would appear that some for of firewall is blocking access to
> bligh's statd from mussel, or that  bligh's statd is ignoring requests
> from mussel.  I don't know which.
> 
> NeilBrown

I'm actually seeing a lot of problems on *ix systems were a service is
registered, but then the corresponding daemon doesn't actually service
requests.

My rpc-health script allowed me to identify a lot of such problems
fairly quickly:

http://dcs.nac.uci.edu/~strombrg/rpc-health.html

...so I guess the upshot is "It isn't necessarily a firewall problem".


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]