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