Date: Wed, 16 Feb 2011 19:28:58 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Michael Proto <mike@jellydonut.org> Cc: george+freebsd@m5p.com, freebsd-stable@freebsd.org Subject: Re: statd/lockd startup failure Message-ID: <20110217032858.GA17686@icarus.home.lan> In-Reply-To: <AANLkTi=2vA=C8B=NEaGrPgGNv2JJr9KEDJps8uoy8_92@mail.gmail.com> References: <201102091420.p19EKJ5u001268@m5p.com> <AANLkTi=2vA=C8B=NEaGrPgGNv2JJr9KEDJps8uoy8_92@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 16, 2011 at 09:46:37PM -0500, Michael Proto wrote: > 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 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 > > > > _______________________________________________ > > 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="-p 898" > rpc_lockd_flags="-p 4045" Yes, this is correct. The NLM error is probably related to the previous errors (possibly due to firewall rule entries, or something that already had bound the port). Some RPC services can be bound to a random port number by default, and on occasion during a reboot two things will try to map to the same port number. It's very annoying when it happens. Running "rpcinfo" on the machine can help determine what's bound to what. Locking down the port numbers as you showed is the best choice, plus allows for proper firewall rules to be added. However, be aware not all daemons support this. Reliable firewall rules for NFS = good luck. -- | 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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110217032858.GA17686>