[wplug] NFS locks + Vpopmail

[Bill Moran]

Christopher DeMarco <cmd at alephant.net> wrote:

> On Fri, Feb 17, 2006 at 09:54:45AM -0500, Mike Griffin wrote:
> 
> > This looks to me like an NFS locking issue. User, group, and
> > permissions are setup correctly on both boxes.
> 
> 1.  Clear your firewall tables on BOTH machines.  If you're running
> NAT, stop ;-) Simplify network access-control.  IIANM NFS v2 uses
> different ports for locking than for read/write.

As Chris is alluding to, NFS uses a LOT of ports for full functionality.
On my FreeBSD desktop, it looks like this:
bash-2.05b$ sockstat -4
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS      
wmoran   soffice.bi 91840 3  tcp4   *:*                   *:*
wmoran   firefox-bi 88335 22 tcp4   172.16.0.40:54207     209.18.34.39:80
wmoran   firefox-bi 88335 30 tcp4   172.16.0.40:55144     209.18.34.39:80
wmoran   sylpheed   93833 8  tcp4   172.16.0.40:55286     66.167.251.6:993
root     sshd       400   3  tcp4   *:22                  *:*
daemon   rpc.lockd  349   3  udp4   *:935                 *:*
daemon   rpc.lockd  349   4  tcp4   *:1005                *:*
daemon   rpc.lockd  349   7  udp4   *:814                 *:*
daemon   rpc.lockd  349   8  udp4   *:876                 *:*
root     rpc.lockd  338   3  udp4   *:935                 *:*
root     rpc.lockd  338   4  tcp4   *:1005                *:*
root     rpc.lockd  338   7  udp4   *:814                 *:*
root     rpc.statd  333   4  udp4   *:694                 *:*
root     rpc.statd  333   5  tcp4   *:624                 *:*
root     rpcbind    278   7  udp4   *:111                 *:*
root     rpcbind    278   8  udp4   *:602                 *:*
root     rpcbind    278   9  tcp4   *:111                 *:*

(note that 'losf -i' on Linux should give you equivalent output)  As
you can see, we have lockd and statd, in additional to rpcbind.  And
they're listening on five different ports.

(While I don't recommend opening up your firewall all the way, you'll
probably need to tweak it a bit to get things working.)

On the Fedora 3 installation (that I seldom use) rpc.lockd isn't starting,
so it's likely that's a default setting.  This would be my first guess as
to what your problem is.  Although Debian could be different.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com