On Fri 8/5/16 21:23 -0400 Ken wrote:
It does occur to me that a firewall can interfere with RPC services, since
you don't know what port the services will end up using; I see "nlockmgr"
running on port 45923 and 43311 on your server, so maybe checking with
tcpdump to see if your client is sending stuff to it and if it is actually
getting received by the server would be useful.
It's working now. Fedora 19 was *not* reading the port values per below config
file:
/etc/sysconfig $ egrep -B1 '^LOCKD' nfs
# TCP port rpc.lockd should listen on.
LOCKD_TCPPORT=32803
# UDP port rpc.lockd should listen on.
LOCKD_UDPPORT=32769
Able to manually fix by running
bash -x /usr/libexec/nfs-utils/scripts/nfs-lock.preconfig
# Sources above 'nfs' config file and then runs:
# /sbin/sysctl -w fs.nfs.nlm_tcpport=$LOCKD_TCPPORT # and another
sysctl for $LOCKD_UDPPORT.
This bug is not in fedora 23.
--
thanks,
Tom
--
$ rpcinfo -p|grep lock
100021 1 udp 32769 nlockmgr
100021 3 udp 32769 nlockmgr
100021 4 udp 32769 nlockmgr
100021 1 tcp 32803 nlockmgr
100021 3 tcp 32803 nlockmgr
100021 4 tcp 32803 nlockmgr
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers