From owner-freebsd-stable@FreeBSD.ORG Wed Mar 9 12:07:58 2011 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 669C61065676 for ; Wed, 9 Mar 2011 12:07:58 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (unknown [IPv6:2001:418:3fd::3]) by mx1.freebsd.org (Postfix) with ESMTP id 36CC58FC14 for ; Wed, 9 Mar 2011 12:07:58 +0000 (UTC) Received: from wonderland.m5p.com (wonderland.m5p.com [IPv6:2001:418:3fd::19]) by mailhost.m5p.com (8.14.3/8.14.3) with ESMTP id p29C7QeJ094643; Wed, 9 Mar 2011 07:07:31 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <4D776D7E.2080908@m5p.com> Date: Wed, 09 Mar 2011 07:07:26 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110217 Thunderbird/3.1.7 MIME-Version: 1.0 To: Daniel Braniss References: <201102091420.p19EKJ5u001268@m5p.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -0.9 () BAYES_00,J_CHICKENPOX_35 X-Scanned-By: MIMEDefang 2.67 on IPv6:2001:418:3fd::f7 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Wed, 09 Mar 2011 07:07:31 -0500 (EST) Cc: freebsd-stable@freebsd.org Subject: Re: statd/lockd startup failure 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: Wed, 09 Mar 2011 12:07:58 -0000 On 03/09/11 03:09, Daniel Braniss wrote: >> Under 8.2-PRERELEASE (GENERIC kernel), about 15% of the times I boot up >> (with rpc.statd and rpc.lockd enabled in rc.conf), I get: >> >> Feb 4 07:31:11 wonderland rpc.statd: bindresvport_sa: Address already in use >> Feb 4 07:31:11 wonderland root: /etc/rc: WARNING: failed to start statd >> >> and slightly later: >> >> Feb 4 07:31:36 wonderland kernel: NLM: unexpected error contacting NSM, stat=5, errno=35 >> >> I can start rpc.statd and rpc.lockd manually at this point (and I have to >> start them to run firefox and mail with my NFS-mounted home directory and >> mail spool). But what might cause the above errors? -- George Mitchell > > We have been seeing this too, with the addition of mountd. > So I decided to try and track it down. > rpc.lockd, rpc.statd or mountd, all share the same code for allocating > address/port. I added some more info to be displayed in case of error, > mainly the ai_family and port, so after many successfull reboots, I got: > > Mar 9 09:18:19 chamsa mountd[1070]: bindresvport_sa: (2/617) Address already > in use > > but: > > chamsa> rpcinfo | grep mountd > 100005 1 udp 0.0.0.0.2.105 mountd superuser > 100005 3 udp 0.0.0.0.2.105 mountd superuser > 100005 1 tcp 0.0.0.0.2.105 mountd superuser > 100005 3 tcp 0.0.0.0.2.105 mountd superuser > > BTW, 0.0.0.2.105 is 617, and 2 is AF_INET > > the above is wierd, since the rpc stuff happens after the bindresvport_sa(...) > > danny > > Thanks for the analysis. The reason I originally posted is to see why this might have popped up in 8.x, as it never happened in 7.x. -- George Mitchell