Date: Tue, 23 Oct 2007 10:59:32 -0500 From: Brooks Davis <brooks@freebsd.org> To: John Marshall <John.Marshall@riverwillow.com.au> Cc: Mike Telahun Makonnen <mtm@freebsd.org>, "freebsd-rc@FreeBSD.Org" <freebsd-rc@freebsd.org> Subject: Re: How to debug rc hangs? Message-ID: <20071023155932.GA37204@lor.one-eyed-alien.net> In-Reply-To: <471DFFD0.8020701@riverwillow.com.au> References: <471D7F68.8070308@riverwillow.com.au> <584bfc3f0710230505i29e8f19aofc4e66d0aee7b7c1@mail.gmail.com> <471DFFD0.8020701@riverwillow.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 24, 2007 at 12:06:08AM +1000, John Marshall wrote: > Mike Telahun Makonnen wrote: > > On 10/23/07, John Marshall <John.Marshall@riverwillow.com.au> wrote: > >> I have tried setting rc_debug=3D"YES" in rc.conf but that doesn't show= me > >> any more than I already know (e.g. last line before mountd hang is: > >> "/etc/rc: DEBUG: run_rc_command: doit: /usr/sbin/mountd -l" > > It seems to me that if it's getting this far, that the problem probably= is > > not in rc.d. The next thing it does after that debug message is eval th= e=20 > > $doit > > line you saw, so either the eval command is missbehaving or the problem > > is with the daemon and not rc.d. What does CTR-t say when it hangs? Als= o, > > I noticed all three programs you listed are network daemons. My guess is > > they are not actually hung, they only *appear* to hang because they're= =20 > > wating > > on some sort of network resource (DNS maybe?). >=20 > Thanks Mike, >=20 > The ctrl-T tip is the kind of information I'm looking for. My primary re= ason=20 > for posting is to find out what tools/switches/hooks are available to he= lp=20 > troubleshoot this kind of problem, rather than asking somebody else to s= olve=20 > it. >=20 > Having said that, ctrl-T shows: > load: 0.74 cmd: mountd 576 [nanslp] 0.00u 0.00s 0% 1428k > load: 0.25 cmd: mountd 576 [nanslp] 0.00u 0.00s 0% 1432k > load: 0.12 cmd: mountd 576 [nanslp] 0.00u 0.00s 0% 1432k >=20 > ...which lends weight to my suspicion that a pre-requisite resource is n= ot=20 > yet available - and, perhaps, hasn't yet started due to a circular=20 > dependency? As I hinted, my plan is to drill down into the PROVIDE/REQUI= RE=20 > labyrinth and work by trial and error (with a reboot in between each err= or).=20 > I'm happy to do that but I'm hoping that I might be able to use this=20 > situation to learn of more elegant ways to diagnose the problem. >=20 > ...and to reiterate, this is on 7.0-BETA1 (built Saturday morning) and a= ll=20 > this was working without any intervention on 6.2-RELEASE. When I see processes stalled on nanslp at boot it's usually when my network= is messed up in some way. I think it's stuck in the resolver trying to look t= hings up. -- Brooks --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHHhpkXY6L6fI4GtQRAkDPAJ4tGbFNBkxilOfUaiEFmzmdEEVdkgCdF4Bi qMFgQjmSxT8hTTNCykN77tk= =S2Vr -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071023155932.GA37204>