NFS volume, lockd not responding

Hello,
I've got two separate computers using two separate NFS shares, exhibiting the same problem.
Here's the summation.
#1
iMac 10.5.6, NFS mounted home directory, connecting to a CentOS 5 box that is under my jurisdiction. The user logs in, but nothing works right. system.log shows "lockd not responding" I've got NFS using reserved ports, but it's not helping. As a temporary work around, this user is using a local account until we can resolve this. There are other Leopard Macs in the same office, connecting to the same NFS volume, and they don't have this problem. This computer was just installed this week.

#2
Mac Pro, 10.5.5 NFS mounted home directory, connecting to some NetApp box, that I don't have admin control of. Same deal, "lockd not responding" There is just the one Mac in this office, so I've got it using local locks until I can find a proper solution.

I see a lot of posts about this, but no clear answer. I've got other Macs in other offices connecting to other NFS volumes without trouble. Where does this problem lie? Is anyone working to fix it?
I'll try and download wireshark and see if I can get anything from it, I've heard a few people figure out something about it, but I haven't yet seen any solid solutions.

Thanks for any leads.
--peter

Posted on Jan 29, 2009 9:11 AM

Reply
Question marked as ⚠️ Top-ranking reply

Posted on Feb 26, 2009 4:23 PM

"lockd not responding" means there is a problem somewhere between the lockd daemon on the NFS client and the lockd daemon on the NFS server. One way or another, lockd requests being made by the NFS client are not getting responses.

This is almost always due to a firewall or NAT on/between the two systems that is keeping the communications from working correctly. The NFSv2/v3 file locking protocols will not work if there is a NAT between the two systems. They will also not work if there is a firewall blocking the communications (either outgoing or incoming).

If only one system is seeing the problem, my first guess is that the firewall on that system is configured such that it is blocking the NFS locking protocol(s). Make sure that SystemPreferences->Security->Firewall is NOT set to "allow only essential services".

HTH
--macko
1 reply
Sort By: 
Question marked as ⚠️ Top-ranking reply

Feb 26, 2009 4:23 PM in response to acranox

"lockd not responding" means there is a problem somewhere between the lockd daemon on the NFS client and the lockd daemon on the NFS server. One way or another, lockd requests being made by the NFS client are not getting responses.

This is almost always due to a firewall or NAT on/between the two systems that is keeping the communications from working correctly. The NFSv2/v3 file locking protocols will not work if there is a NAT between the two systems. They will also not work if there is a firewall blocking the communications (either outgoing or incoming).

If only one system is seeing the problem, my first guess is that the firewall on that system is configured such that it is blocking the NFS locking protocol(s). Make sure that SystemPreferences->Security->Firewall is NOT set to "allow only essential services".

HTH
--macko
Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

NFS volume, lockd not responding

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.