From owner-freebsd-stable@FreeBSD.ORG Tue Mar 1 06:48:08 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 59972106564A for ; Tue, 1 Mar 2011 06:48:08 +0000 (UTC) (envelope-from ml@netfence.it) Received: from cp-out7.libero.it (cp-out7.libero.it [212.52.84.107]) by mx1.freebsd.org (Postfix) with ESMTP id DBCA48FC08 for ; Tue, 1 Mar 2011 06:48:07 +0000 (UTC) X-CTCH-Spam: Unknown X-CTCH-RefID: str=0001.0A0B0201.4D6C96A6.00B7,ss=1,re=0.000,fgs=0 X-libjamoibt: 1555 Received: from soth.ventu (151.51.54.55) by cp-out7.libero.it (8.5.133) id 4D63CB8F00E8E55E for freebsd-stable@freebsd.org; Tue, 1 Mar 2011 07:48:06 +0100 Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.4/8.14.4) with ESMTP id p216lcGM067184 for ; Tue, 1 Mar 2011 07:47:38 +0100 (CET) (envelope-from ml@netfence.it) Message-ID: <4D6C968A.3040400@netfence.it> Date: Tue, 01 Mar 2011 07:47:38 +0100 From: Andrea Venturoli User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; it-IT; rv:1.9.2.13) Gecko/20101211 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <201102091420.p19EKJ5u001268@m5p.com> <20110217032858.GA17686@icarus.home.lan> <4D5D8DF0.8080900@netfence.it> In-Reply-To: <4D5D8DF0.8080900@netfence.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.1.2.13 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: Tue, 01 Mar 2011 06:48:08 -0000 On 02/17/11 22:06, Andrea Venturoli wrote: >> I >>> seem to remember a similar problem I had a long time ago. I opted to >>> use a consistent, not-used port and haven't seen the problem since >>> (this was years ago, so I can't remember if the error you're seeing >>> was identical to mine). >>> >>> /etc/rc.conf: >>> rpc_statd_flags="-p 898" >>> rpc_lockd_flags="-p 4045" > > I have: > rpc_statd_flags="-p 918" > rpc_lockd_flags="-p 868" > > > Still statd occasionally fails to start. > > It might be that something else has already bound to port 918, though I > don't know what. > I'll check as soon as I have the chance. It happened this morning: lockd could not start and I verified it was an NFS mount which used port 868 as a client. Now I'm trying the noresvport to mount_nfs... bye av.