From owner-freebsd-current@FreeBSD.ORG Sun May 1 21:37:55 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97FAA1065672 for ; Sun, 1 May 2011 21:37:55 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 51FD18FC1E for ; Sun, 1 May 2011 21:37:54 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEACLSvU2DaFvO/2dsb2JhbACEUaJDiHGoaY9HgSqDVYEBBI55jj4 X-IronPort-AV: E=Sophos;i="4.64,299,1301889600"; d="scan'208";a="119252416" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 01 May 2011 17:37:53 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 9A740B3F98; Sun, 1 May 2011 17:37:53 -0400 (EDT) Date: Sun, 1 May 2011 17:37:53 -0400 (EDT) From: Rick Macklem To: Garrett Cooper Message-ID: <1964919189.836346.1304285873572.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Cc: FreeBSD Current Subject: Re: "RPC: program not registered" with new NFS server? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2011 21:37:55 -0000 > Hi Rick, et all, > I upgraded to a later kernel on two of my machines and am running > into issues starting up the nfs kernel. Every time I try mounting like > so: > > # mount -t nfs localhost:/scratch/ /mnt/ > > or like so: > > # mount -t oldnfs localhost:/scratch/ /mnt/ > > I run into this error: > > [tcp] localhost:/scratch: RPCPROG_NFS: RPC: Program not registered > [tcp6] localhost:/scratch: RPCPROG_NFS: RPC: Program not registered > > I kldloaded nfsd, and then could start the mountd and nfsd > services (this made some of my problems go away, in particular > showmount -e looks sane), but things aren't sane. I know that nfs > client capability works because I can mount remote NFS shares via amd > and raw nfs mounts with another machine that I haven't upgraded and > things are fine, but the server appears to be completely broken on my > machines. > Here is the configuration: > > $ grep NFS /root/FALLOUT > #options NFSCL > #options NFSCLIENT # Network Filesystem Client > #options NFSSERVER # Network Filesystem Server > #options NFSLOCKD # Network Lock Manager > #options NFS_ROOT # NFS usable as /, requires NFSCLIENT > $ grep nfs /etc/src.conf > MODULES_OVERRIDE+= krpc nfscommon nfscl nfsclient nfsd nfslockd > nfsserver > > # rc.conf snippet... > > rpcbind_enable="YES" > mountd_enable="YES" > rpc_lockd_enable="YES" > rpc_statd_enable="YES" > nfsd_enable="YES" > Well, I think the rc variable has always been: nfs_server_enable="YES" which still works for the new one as well as old one. The only other thing I can think of is if you are pre-r220510 you need to create an empty stablerestart file before the new nfs server will start. Take a look to see if the nfsd is running via "ps axHl" or similar and check /var/log/messages for nfsd/mountd related errors. If you need to create the stable restart file, just do the following on the server: # install -o root -g wheel -m 600 /dev/null /var/db/nfs-stablerestart (This shouldn't be necessary for post r220510 systems and pre-r220510 systems shouldn't try and run the new server by default, so this shouldn't be your problem. Just "ls -l /var/db" to see if the file is there.) rick