From owner-freebsd-stable@FreeBSD.ORG  Wed Mar  9 08:09:26 2011
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 BE7C0106564A
	for <freebsd-stable@freebsd.org>; Wed,  9 Mar 2011 08:09:26 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84])
	by mx1.freebsd.org (Postfix) with ESMTP id 71F028FC12
	for <freebsd-stable@freebsd.org>; Wed,  9 Mar 2011 08:09:26 +0000 (UTC)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by kabab.cs.huji.ac.il with esmtp
	id 1PxESS-000PIG-5p; Wed, 09 Mar 2011 10:09:24 +0200
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: george+freebsd@m5p.com
In-reply-to: <201102091420.p19EKJ5u001268@m5p.com> 
References: <201102091420.p19EKJ5u001268@m5p.com>
Comments: In-reply-to george+freebsd@m5p.com
	message dated "Wed, 09 Feb 2011 09:20:19 -0500."
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 09 Mar 2011 10:09:24 +0200
From: Daniel Braniss <danny@cs.huji.ac.il>
Message-ID: <E1PxESS-000PIG-5p@kabab.cs.huji.ac.il>
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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2011 08:09:26 -0000

> 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