Josh,
I think the first statement is true. I have many items monitored by hobbit
which are not registered in DNS (I live with a bunch of windows centric team
mates and they rely on WINS not DNS. None of these items end up with
conn=red, but they are ID'd in the output from bbtest on the hobbit server.
Here is that output:
DNS statistics:
# hostnames resolved : 383
# succesful : 306
# failed : 77
# calls to dnsresolve : 414
Notice that I have 77 monitored items which fail the DNS lookup.
.....Bruce
From: Josh Luthman [mailto:user-4c45a83f15cb@xymon.invalid]
Sent: Wednesday, March 19, 2008 8:55 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] How hobbit server deal with DNS server failure when
doing conn test ?
Pretty confident if the DNS lookup fails it times out and marks the conn red
=( If you don't need it to do a DNS lookup simply add testip.
On 3/19/08, T.J. Yang <user-8e841282cda5@xymon.invalid <mailto:user-8e841282cda5@xymon.invalid> >
wrote:
I remember somewhere in the manpages,
The hobbit server when doing fping conn test, it will try using FQDN and if
not resolvable,
it will use the ip address(from bb-hosts) file.
Is this a correct statement ?
I will summarize the answer here
http://en.wikibooks.org/wiki/System_Monitoring_with_Hobbit/Other_Docs/FAQ#Ho
w_does_the_conn_test_work_if_the_first_ping_doesn.27t_respond_.3F
<http://en.wikibooks.org/wiki/System_Monitoring_with_Hobbit/Other_Docs/FAQ#H
ow_does_the_conn_test_work_if_the_first_ping_doesn.27t_respond_.3F>
tj
--
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
Those who don't understand UNIX are condemned to reinvent it, poorly.
--- Henry Spencer
Note: The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this message is
not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and deleting it from
your computer. Thank you. Fellowes, Inc.