NFS lockd problem

[Ronald Klop]

On Fri, 26 Mar 2010 12:08:26 +0200, Giulio Ferro <auryn at zirakzigil.org>  
wrote:

> Outset:
> 1 NFS server (with lockd)
> 2 NFS client (with lockd)
>
> The clients serve several jails with apache, whose data (www) resides on  
> the server
>
>  From time to time everything seem to freeze. Then, after one minute or  
> so, the system
> works again as nothing had happened.
>
> In these occasions I get this in the logs on the client madchines:
> Mar 26 10:29:38 virt1 kernel: nfs server  
> 192.168.40.121:/data/mount_servers/wwwsec/www: lockd not responding
>
> followed shortly after by:
>
> Mar 26 10:29:38 virt1 kernel: nfs server  
> 192.168.40.121:/data/mount_servers/wwwsec/www: lockd is alive again
>
>
> On the server I only get this:
> Mar 26 10:29:31 data1 kernel: NLM: failed to contact remote rpcbind,  
> stat = 5, port = 28416
>
> I don't think it's a network problem, since all connections are local  
> and high speed (1Gb/s)
>
> I must admit that, with the other nfs problem I reported weeks ago, this  
> kind of freebsd system seems
> less than stable to me, and this is very disappointing...
>
> Anyway I'd appreciate any pointer on this issue...

I'm no NFS expert, so I don't know if I can help, but regularly people  
want to know your FreeBSD version(s), your used NFS version, if you are  
running NFS over TCP or UDP. Does it help to switch between UDP/TCP?

Ronald.