Re: NFS issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



No firewall on either end and server responds to ping.

client:
  program vers proto   port
   100000    2   tcp    111  portmapper
   100000    2   udp    111  portmapper
   100024    1   udp    889  status
   100024    1   tcp    892  status
server:

  program vers proto   port
   100000    2   tcp    111  portmapper
   100000    2   udp    111  portmapper
   100024    1   udp    964  status
   100024    1   tcp    967  status
   100011    1   udp    718  rquotad
   100011    2   udp    718  rquotad
   100011    1   tcp    721  rquotad
   100011    2   tcp    721  rquotad
   100003    2   udp   2049  nfs
   100003    3   udp   2049  nfs
   100003    4   udp   2049  nfs
   100021    1   udp  32768  nlockmgr
   100021    3   udp  32768  nlockmgr
   100021    4   udp  32768  nlockmgr
   100003    2   tcp   2049  nfs
   100003    3   tcp   2049  nfs
   100003    4   tcp   2049  nfs
   100021    1   tcp  58027  nlockmgr
   100021    3   tcp  58027  nlockmgr
   100021    4   tcp  58027  nlockmgr
   100005    1   udp    778  mountd
   100005    1   tcp    781  mountd
   100005    2   udp    778  mountd
   100005    2   tcp    781  mountd
   100005    3   udp    778  mountd
   100005    3   tcp    781  mountd

However I just rebooted the nfs server. But when I checked before lockd was running with a ps -A As Craig said he started notice this about the the time he upgraded to 5.2, the same goes for me, started getting this problem about the time I've upgraded the clients and server.
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)

nate

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos


--

*Johan Swensson | apegroup*
System Administrator
johan@xxxxxxxxxxxx
Mobile: +46 (0) 735 21 98 58
www.apegroup.com
Fiskartorpsvägen 52, 115 42 Stockholm
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux