rpc.statd is basically broken due to the new security "enhancements" added in RH 7.0. In effect, any lock requests to rpc.lockd fail because rpc.statd can't "monitor" anything. This is due to rpc.statd not being able to do just about anything after it starts (like accessng files). The reason is that rpc.statd now chdirs to /var/lib/nfs/statd (which is fine), then CHROOTS to "." !! Well, needless to say after the chroot not much works since it can no longer access /etc, /usr/lib, etc. I would suggest either removing the questionable "chroot" call or making sure when installing that a full "anon ftp" sort of environment exists under /var/lib/nfs/statd
Created attachment 12667 [details] strace showing statd system calls (and failures)
*** This bug has been marked as a duplicate of 31801 ***