fam
[Top] [All Lists]

Re: FAM not notifying of non-local changes on NFS files

To: fam@xxxxxxxxxxx
Subject: Re: FAM not notifying of non-local changes on NFS files
From: Michael Wardle <michael.wardle@xxxxxxxxxx>
Date: 15 Apr 2003 10:34:42 +1000
In-reply-to: <3E9B4EB8.1050107@xxxxxxxx>
Organization: Adacel Technologies
References: <3E96F39E.1090105@xxxxxxxx> <1050276396.2229.6.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <3E9B4EB8.1050107@xxxxxxxx>
Sender: fam-bounce@xxxxxxxxxxx
On Tue, 2003-04-15 at 10:13, Ken Tanzer wrote:
> I took the "bind" entry out as suggested, and it doesn't seem to help.  
> I don't think that setting should matter anyway, as we're not trying to 
> use FAM on a non-local machine.

It will matter on the server, I think.  I can't see how it would matter
on the client, but you might like to try it there as well, just in case.

>   The only thing running on a non-local 
> machine is the NFS server.  Here's a bad diagram:
> 
> MACHINE A
> FAM Client Running
> FAM Server Running
> Watching  /mnt/nfs/somedir-->NFS---->/somedir/somefile
>                                      NFS Server
>                                      MACHINE B
> 
>  From Machine A, "touch /mnt/nfs/somedir/somefile" is picked up by FAM.
> When you do "touch /somedir/somefile" from Machine B, nothing happens.
> 
> I've been wondering if this is the same problem described in FAM bug 
> #166 ("Pollster broken by DNotify patch", 
> http://oss.sgi.com/bugzilla/show_bug.cgi?id=166).

This should only apply if your kernel does not provide the DNotify API. 
Red Hat has only used the DNotify patch on versions of their
distributions using Linux kernel 2.4 and higher, so provided you are
also using a 2.4 or higher kernel, I'm not sure that this bug affects
you.

Maybe it would be useful for me to write another test script that tests
whether a local famd can connect to -- and get updates from -- a remote
famd.

Thanks for mentioning this problem to me.  I'm glad you're investigating
the possible causes, but I don't think we've yet hit it on the head.

Some other things I'd suggest trying are:
- running famd with the debug flag (-d) on the server and the client
- ensuring the sgi_fam service is registered on the server using portmap
- ensuring fam is not blocked by firewalling or tcp wrappers
- ensuring the contents of /etc/mtab and /etc/exports are sane
- monitoring network traffic using tcpdump

I haven't used the NFS functionality in FAM for a while now (partly
because all my Linux servers are running Red Hat which disables FAM
networking out of the box).  I'll have a look at it myself when time
permits, but this isn't likely to be soon.

Thanks and good luck

-- 
Michael Wardle <michael.wardle@xxxxxxxxxx>
Adacel Technologies


<Prev in Thread] Current Thread [Next in Thread>