Aha! Ok, thanks.
I made the mistake of running that manually, and it kind of short
circuited every CONN test out there on the running server. Oops.
More pager batteries........................
Kent C. Brodie - user-da7f7d5174c0@xymon.invalid
Department of Physiology
Medical College of Wisconsin
(XXX) XXX-XXXX
-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: Monday, July 24, 2006 3:56 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] DNS resolution
On Mon, Jul 24, 2006 at 03:35:47PM -0500, Brodie, Kent wrote:
Hi- by the way, my cluster stuff is finally working the way I want.
Thanks for putting up with my ignorance on how the hobbitd and bbproxy
stuff co-exist (or don't)!
In my bbtests column of my main server, I see:
DNS statistics:
# hostnames resolved : 141
# succesful : 136
# failed : 5
# calls to dnsresolve : 183
.... any idea what's the easiest way for me to discern "which" of my
183
hosts are failing DNS resolution?
The only way currently is to run bbtest-net with the --debug option, and
grep the output for "DNS lookup failed". I've been asked before, so I
really should add some way of easily finding this information, or at
least provide a way of logging it.
BTW, you don't have 183 hostnames - you have 141. The 183 is the number
of times a hostname lookup was done, so some of them was via the cache
that bbtest-net has. This is because the same hostname may be needed for
multiple tests, e.g. if you use it in http url's that you test.
Regards,
Henrik