From owner-freebsd-stable@FreeBSD.ORG Mon Mar 29 16:56:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7C14106564A for ; Mon, 29 Mar 2010 16:56:49 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id 88FF28FC0A for ; Mon, 29 Mar 2010 16:56:49 +0000 (UTC) Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta13.westchester.pa.mail.comcast.net with comcast id yz4G1d0041HzFnQ5D4wpLk; Mon, 29 Mar 2010 16:56:49 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta14.westchester.pa.mail.comcast.net with comcast id z4wo1d00P3S48mS3a4wpT7; Mon, 29 Mar 2010 16:56:49 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8CF989B419; Mon, 29 Mar 2010 09:56:47 -0700 (PDT) Date: Mon, 29 Mar 2010 09:56:47 -0700 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20100329165647.GA3796@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Strange NFS-related messages (related to lockd/statd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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 Mar 2010 16:56:49 -0000 I recently brought up rpc.lockd and rpc.statd on all of our NFS clients (mixed RELENG_6, RELENG_7, and RELENG_8), and our NFS server (RELENG_8). All clients had nfs_client_enable="yes" in rc.conf prior to their last reboot, but lacked rpcbind_enable="yes", rpc_lockd_enable="yes", and rpc_statd_enable="yes" prior to the below. The 8.x clients started rpcbind, rpc.lockd, rpc.statd -- then said: NLM: failed to contact remote rpcbind, stat = 0, port = 0 Can't start NLM - unable to contact NSM The 7.x clients started rpcbind, rpc.lockd, rpc.statd -- then said: Can't start NLM - unable to contact NSM One of the 7.x clients also kernel panic'd when starting rpc.lockd, in some nlm_* kernel functions. Looking at commits showed that the bug that caused the panic was fixed in a later 7.x release. The 7.x clients started rpcbind, rpc.lockd, rpc.statd -- and said nothing. The above daemons were all started in that order, per the FreeBSD Handbook. I can't find a definition of what the acronyms NLM and NSM stand for, nor does Googling the error messages return relevant results (except one FreeBSD committer reporting similar, but nobody replied). I don't know the implications of these messages. The only thing I can think might cause such errors would be the fact that these machines all have dual NICs with firewall rules applied only to their primary (WAN-side) interface. The NFS server exists only on the private (LAN-side) interface. I'm thinking rpcbind may have tried to "do stuff" on the WAN interface, since no -h option was applied. I haven't tried making use of -h yet, nor have I tried restarting the daemons to see if the errors recur (or if it was just a one-time thing). Any information/tips/advice would be appreciated. Danke! -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |