From owner-freebsd-stable@FreeBSD.ORG Sun Dec 28 19:43:27 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDFB016A4CE for ; Sun, 28 Dec 2003 19:43:27 -0800 (PST) Received: from doom.homeunix.org (8-248.dialup.comset.net [213.172.8.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69DC943D55 for ; Sun, 28 Dec 2003 19:43:03 -0800 (PST) (envelope-from igor@doom.homeunix.org) Received: from doom.homeunix.org (localhost [127.0.0.1]) by doom.homeunix.org (8.12.10/8.12.10) with ESMTP id hBT3gTAT000749; Mon, 29 Dec 2003 06:42:36 +0300 (MSK) (envelope-from igor@doom.homeunix.org) Received: (from igor@localhost) by doom.homeunix.org (8.12.10/8.12.10/Submit) id hBT3gLaQ000748; Mon, 29 Dec 2003 06:42:21 +0300 (MSK) (envelope-from igor) Date: Mon, 29 Dec 2003 06:42:21 +0300 From: Igor Pokrovsky To: Rob Message-ID: <20031229034221.GA671@doom.homeunix.org> Mail-Followup-To: Rob , freebsd-stable@freebsd.org References: <3FEECA99.4030603@users.sourceforge.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FEECA99.4030603@users.sourceforge.net> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org Subject: Re: NFS problem: "RPC: Port mapper failure" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 03:43:28 -0000 On Sun, Dec 28, 2003 at 09:20:41PM +0900, Rob wrote: > > Hi, > > I am running two FreeBSD-Stable PCs. > > One is an NFS server and the other NFS client. Everything used to > work fine until recently. I suspect that either the new kernel is the > problem (although there are no complaints on the stable mailing list) > or the network administration has changed some things. > > The server is on 147.46.44.183 with following /etc/exports: > /usr/ports -maproot=root 147.47.254.184 > /home/entertainment -ro 147.47.254.184 > > The server boots with rc.conf: > nfs_reserved_port_only="YES" > portmap_enable="YES" > nfs_server_enable="YES" > mountd_flags="-r" > > The client boots with rc.conf: > nfs_reserved_port_only="YES" > nfs_client_enable="YES" > > On the client (147.47.254.184) I do not get the proper response on: > $ showmount -e 147.46.44.183 > RPC: Port mapper failure > showmount: can't do exports rpc > > Doing a mount_nfs on the client, gives the same port mapper failure. > > Portmap is running on the server; it is not on the client, but > that should be OK here, right? > > I am at a total loss, since I have no idea how to investigate further > what is actually going wrong. What could be a reason for the RPC Port > mapper failure? How else can I test the port mapper's functunality? You can try to check if nfsd and portmap really started on server: sockstat | grep portmap and sockstat | grep nfsd -ip -- "Well," Brahma said, "even after ten thousand explanations, a fool is no wiser, but an intelligent man requires only two thousand five hundred." -- The Mahabharata.