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
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
