strange result in fping by hobbit and fping by yours truly

What was suggested was that you have something like

172.16.1.50 terminal150.notmydomain.com #

Here Hobbit is attempting to resolve terminal150.notmydomain.com, fails, and
then pings the IP address.  Since you know the IP and it isn't going to
change, try

172.16.1.50 terminal150.notmydomain.com # testip

See if that resolves your issue.  Note you can click on the host on the web
interface and it will say the IP it is pinging.

On 11/2/07, Hobbit User <user-24d6f8323faa@xymon.invalid> wrote:

You're aware, aren't you, that unless you have "testip" keyword on the
bb-hosts line, hobbit DNS resolves the bb-hosts name and uses the bb-hosts
IP only if the name lookup fails?

On Fri, November 2, 2007 11:28, Dennis Ortsen wrote:

These terminals are not in DNS. There's also a large amount of Cisco
accesspoints that are fpinged the same way. These AP's are also not in
DNS.
The number of AP's is even larger than the number of terminals: 247.

-----Oorspronkelijk bericht-----
Van: Hubbard, Greg L [mailto:user-d970b5e56ec9@xymon.invalid]
Verzonden: vrijdag 2 november 2007 15:21
Aan: user-ae9b8668bcde@xymon.invalid
Onderwerp: RE: [hobbit] strange result in fping by hobbit and
fping by yours truly

DNS?

-----Original Message-----
From: Dennis Ortsen [mailto:user-8b22a8e3a886@xymon.invalid]
Sent: Friday, November 02, 2007 7:47 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] strange result in fping by hobbit and fping
by yours truly


Hi everyone,

I've got a somewhat strange issue with fping in hobbit.

I've got a list of about 122 terminals that are used for a chipcard
payment system. Each one of them has an ip-address and connects to a
server to process the payments. Every now and then the terminals loose
the connection or whatever, they need to be reset before they can
process the payments again on the server. I thought I might use Hobbit
to ping all the terminals to see if they still respond to a ping. If
they don't reply anymore, they need a reset.

I only do a conn test on an ip-address. I use the full path
to fping in
hobbitserver.cfg, without any extra parameters. When hobbit starts
testing the connection, only 14 terminals respond to a ping,
but when I
execute a fping myself (as the hobbit user) in a shell to the same
amount of terminals, I get a totally different result, instead of 14
responding terminals, I get 95 responding terminals with
fping! It's not
just a lucky shot, I can keep on trying these terminals, the huge
difference remains whether I fping them myself or when hobbit fpings
them.

I'm running hobbit 4.2.0. According to bbtest I have 806
hosts that are
pinged, that takes about 26 seconds to complete. To complete all tests
(954), it takes about 47 seconds.

Does anyone have a clue why specifically these terminals have such a
difference in hobbit ping and a ping performed by myself?

I can't explain it, and it doesn't seem like a timeout (latency) issue
to me either.

Thanks in advance,

Br.

Dennis

-- 
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