[CentOS] NFS issues

[Craig White]

On Tue, 2008-08-12 at 20:16 -0700, nate wrote:
> Johan Swensson wrote:
> > It happend again this night but now I temporarily(?) fixed it with
> > mounting -o nolock on the web servers.
> > It works but dmesg is still spamming "lockd: server 192.168.20.22 not
> > responding, timed out". Atleast my sites are up, and the message isn't
> > critical anymore.
> > But how can I get rid of it?
> 
> What does 'rpcinfo -p' read on both the servers and the clients?
> 
> Also how about /etc/init.d/nfs status (both client and server)
> and /etc/init.d/nfslock status (both client and server)
> 
> Any firewalls in between client and server?
> Run: iptables -L -n (on both client and server)
----
I don't want to step on Johan's thread but wanted to commiserate with
him.

No firewall's at present...
nfs and nfslock on both client and server are running and show pid's

client
[root at cube ~]# rpcinfo -p                                   
   program vers proto   port  service                       
    100000    4   tcp    111  portmapper                    
    100000    3   tcp    111  portmapper                    
    100000    2   tcp    111  portmapper                    
    100000    4   udp    111  portmapper                    
    100000    3   udp    111  portmapper                    
    100000    2   udp    111  portmapper                    
    100000    4     0    111  portmapper                    
    100000    3     0    111  portmapper                    
    100000    2     0    111  portmapper                    
    100024    1   udp  50259  status                        
    100024    1   tcp  53710  status                        
    100021    1   tcp  53045  nlockmgr                      
    100021    3   tcp  53045  nlockmgr                      
    100021    4   tcp  53045  nlockmgr                      

server
[root at srv1 log]# rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp   4003  status
    100024    1   tcp   4003  status
    100011    1   udp   4000  rquotad
    100011    2   udp   4000  rquotad
    100011    1   tcp   4000  rquotad
    100011    2   tcp   4000  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100021    1   udp   4001  nlockmgr
    100021    3   udp   4001  nlockmgr
    100021    4   udp   4001  nlockmgr
    100021    1   tcp   4001  nlockmgr
    100021    3   tcp   4001  nlockmgr
    100021    4   tcp   4001  nlockmgr
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100005    1   udp   4002  mountd
    100005    1   tcp   4002  mountd
    100005    2   udp   4002  mountd
    100005    2   tcp   4002  mountd
    100005    3   udp   4002  mountd
    100005    3   tcp   4002  mountd

Server has ports fixed in place with settings in /etc/sysconfig/nfs

Craig