Date: Mon, 23 Jun 2014 20:28:29 +0300 From: Beeblebrox <zaphod@berentweb.com> Cc: freebsd-current Current <freebsd-current@freebsd.org> Subject: Re: Previously working PXE setup now fails Message-ID: <20140623202829.072ee954@rsbsd.rsb> In-Reply-To: <CAG=rPVciV=S8cJ67mF1qbG1yMJH_JnTCxyfSWEL-0YN2DGPTiQ@mail.gmail.com> References: <1402410667736-5919662.post@n5.nabble.com> <CAG=rPVciV=S8cJ67mF1qbG1yMJH_JnTCxyfSWEL-0YN2DGPTiQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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=3D0 -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=3D"-h 192.168.2.1" mountd_flags=3D"-r -n -l -h 192.168.2.1" nfsd_flags=3D"-u -t -n 4 -h 192.168.2.1" nfsv4_only=3D"YES" nfsv4_server_enable=3D"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=3D"YES" rpc_statd_enable=3D" 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. --=20 FreeBSD_amd64_11-Current_RadeonKMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140623202829.072ee954>