Re: Previously working PXE setup now fails

From: Beeblebrox <zaphod_at_berentweb.com>
Date: Mon, 23 Jun 2014 20:28:29 +0300
> see if you can run wireshark on your NFS server that is being mounted.
> That should narrow down the RPC error.

It took a while to get around to this, but the problem looks like NFS
v3 - v4 conflict. Wireshark shows these errors:
Program Version: 3 \ V3 Procedure: MNT (1) \Status: ERR_ACCESS (13)

But NFS is started as v4. /etc/exports (not sure if correct syntax):
V4:  /     -network 192.168.2.0/26
/data/amd64     -ro -network 192.168.2.0/26		# NFS root
/usr/local      -ro -maproot=0 -network 192.168.2.0/26
/home           -network 192.168.2.0/26

The PXE structure (dhcp & tftp) are started as a jail with the jail
root folder as the NFS export root (/data/amd64). The jail and NFS
services are not started with boot but with separate script.

/etc/rc.conf has:
rpcbind_flags="-h 192.168.2.1"
mountd_flags="-r -n -l -h 192.168.2.1"
nfsd_flags="-u -t -n 4 -h 192.168.2.1"
nfsv4_only="YES"
nfsv4_server_enable="YES"

pxe_start_script.sh:
jail -c pxe
service rpcbind onestart
service mountd onestart
service nfsd onestart
service nfsuserd onestart
# disabled_not_needed? rpc_lockd_enable="YES"  rpc_statd_enable="

I should probablymove the rc.conf flags into my pxe_start_script.sh,
but not sure how to pass "service start" flags in an sh script.

Regards.

-- 
FreeBSD_amd64_11-Current_RadeonKMS
Received on Mon Jun 23 2014 - 15:28:27 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:50 UTC