On Thu, Jul 16, 2015 at 12:02:43AM -0453, William A. Mahaffey III wrote:
4256EE1 # rc.d/nfsd start
Starting nfsd.
4256EE1 # rc.d/nfsd status
nfsd is not running.
4256EE1 # rpcinfo
rpcinfo: Can't contact rpcbind (: RPC: Remote system error - No such
file or directory)
OK, this is bad. Is rpcbind actually running? You have to have that
for nfs to work. Work on getting rpcinfo returning valid information,
that is the foundation for everything else. Once rpcinfo is reporting
something like this:
[blymn@siren] rpcinfo
program version netid address service owner
100000 4 tcp 0.0.0.0.0.111 portmapper superuser
100000 3 tcp 0.0.0.0.0.111 portmapper superuser
100000 2 tcp 0.0.0.0.0.111 portmapper superuser
100000 4 udp 0.0.0.0.0.111 portmapper superuser
100000 3 udp 0.0.0.0.0.111 portmapper superuser
100000 2 udp 0.0.0.0.0.111 portmapper superuser
100000 4 tcp6 ::.0.111 portmapper superuser
100000 3 tcp6 ::.0.111 portmapper superuser
100000 4 udp6 ::.0.111 portmapper superuser
100000 3 udp6 ::.0.111 portmapper superuser
100000 4 local /var/run/rpcbind.sock portmapper superuser
100000 3 local /var/run/rpcbind.sock portmapper superuser
100000 2 local /var/run/rpcbind.sock portmapper superuser
100005 1 udp 0.0.0.0.3.254 mountd superuser
100005 3 udp 0.0.0.0.3.254 mountd superuser
100005 1 tcp 0.0.0.0.3.255 mountd superuser
100005 3 tcp 0.0.0.0.3.255 mountd superuser
100005 1 udp6 ::.3.254 mountd superuser
100005 3 udp6 ::.3.254 mountd superuser
100005 1 tcp6 ::.3.255 mountd superuser
100005 3 tcp6 ::.3.255 mountd superuser
100003 2 udp 0.0.0.0.8.1 nfs superuser
100003 3 udp 0.0.0.0.8.1 nfs superuser
100003 2 tcp 0.0.0.0.8.1 nfs superuser
100003 3 tcp 0.0.0.0.8.1 nfs superuser
100003 2 udp6 ::.8.1 nfs superuser
100003 3 udp6 ::.8.1 nfs superuser
100003 2 tcp6 ::.8.1 nfs superuser
100003 3 tcp6 ::.8.1 nfs superuser
then it is likely that nfs will Just Work (tm).