Date: Wed, 16 Feb 2011 21:46:37 -0500 From: Michael Proto <mike@jellydonut.org> To: george+freebsd@m5p.com Cc: freebsd-stable@freebsd.org Subject: Re: statd/lockd startup failure Message-ID: <AANLkTi=2vA=C8B=NEaGrPgGNv2JJr9KEDJps8uoy8_92@mail.gmail.com> In-Reply-To: <201102091420.p19EKJ5u001268@m5p.com> References: <201102091420.p19EKJ5u001268@m5p.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 9, 2011 at 9:20 AM, <george+freebsd@m5p.com> 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 =A04 07:31:11 wonderland rpc.statd: bindresvport_sa: Address already = in use > Feb =A04 07:31:11 wonderland root: /etc/rc: WARNING: failed to start stat= d > > and slightly later: > > Feb =A04 07:31:36 wonderland kernel: NLM: unexpected error contacting NSM= , stat=3D5, errno=3D35 > > 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). =A0But what might cause the above errors? =A0 -- George Mitc= hell > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Don't rpc.statd and lockd try to choose a random port upon startup? 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=3D"-p 898" rpc_lockd_flags=3D"-p 4045" -Proto
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=2vA=C8B=NEaGrPgGNv2JJr9KEDJps8uoy8_92>