Xymon Mailing List Archive search

Conn test problems

list Michael A. Price
Wed, 9 Jan 2008 11:58:03 -0500
Message-Id: <user-c4403b10dda9@xymon.invalid>

My 'ping test completed' goes through the roof if my #trace tag is in
the monitoring field and the host is down...

 
It keeps trying to trace route and it times out..

 
Never found a fix..

 
From: Josh Luthman [mailto:user-4c45a83f15cb@xymon.invalid] Sent: Wednesday, January 09, 2008 10:55 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] Re: Conn test problems

 
Has anyone else encountered issues like this?  Has anyone else
encountered any similar issues with all the conn tests going haywire?

I figured I'd also post this information while "bumping" the email:

bbgen for Hobbit version 4.2.0


Statistics:

 Hosts               :   164

 Status messages     :   531

 Purple messages     :     0

 Pages               :     1


TIME SPENT

Event                                            Starttime
Duration


Startup                                  1199894029.525853
• Load links done                          1199894029.526327
0.000474 
Load bbhosts done                        1199894029.531645
          0.005318 
ACK removal done                         1199894029.531742
0.000097 
Load STATE done                          1199894029.563429
0.031687 
Color calculation done                   1199894029.563629          0.000200 
Hobbit pagegen start                     1199894029.563659
0.000030 
Hobbit pagegen done                      1199894029.573544
0.009885 
BB2 generation done                      1199894029.576605          0.003061 
BBNK generation done                     1199894029.577261
0.000656 
Summary transmission done                1199894029.577265
0.000004 
WML generation done                      1199894029.578793          0.001528 
Run completed                            1199894029.578798
0.000005 
TIME TOTAL
0.052945 
 
bbtest-net version 4.2.0

SSL library : OpenSSL 0.9.8b 04 May 2006

LDAP library: OpenLDAP 20327


Statistics:

 Hosts total           :      161

 Hosts with no tests   :        1

 Total test count      :      181

 Status messages       :      182


 Alert status msgs     :        0

 Transmissions         :        3


DNS statistics:

 # hostnames resolved  :       16

 # succesful           :       16

 # failed              :        0

 # calls to dnsresolve :       27


TCP test statistics:

 # TCP tests total     :       13

 # HTTP tests          :        5

 # Simple TCP tests    :        8

 # Connection attempts :       13

 # bytes written       :      780

 # bytes read          :    22792


TIME SPENT

Event                                            Starttime
Duration

bbtest-net startup                       1199893834.785076
• Service definitions loaded               1199893834.787463          0.002387
Tests loaded                             1199893834.793085
0.005622 
DNS lookups completed                    1199893834.883042
0.089957 
Test engine setup completed              1199893834.886789          0.003747 
TCP tests completed                      1199893835.028904
0.142115 
PING test completed (160 hosts)          1199893870.087696
35.058792 
PING test results sent                   1199893870.090125          0.002429 
Test result collection completed         1199893870.090173
0.000048 
LDAP test engine setup completed         1199893870.090175
0.000002 
LDAP tests executed                      1199893870.090177          0.000002 
LDAP tests result collection completed   1199893870.090179
0.000002 
NSLOOKUP tests executed                  1199893870.244778
0.154599 
Test results transmitted                 1199893870.246478          0.001700 
bbtest-net completed                     1199893870.248556
0.002078 
TIME TOTAL
35.463480


On 1/7/08, Josh Luthman <user-4c45a83f15cb@xymon.invalid> wrote:

I've been getting a lot of these recently.  A lot of the time I'll get a
good 3/4 of the hosts I'm monitoring like this, other days it is just
one or two.  I can't seem to find any pattern to it.  I'm very confident
it isn't network related as it happens to the first entry, Hobbit
server.  I just can't imagine why it would have issues getting to
127.0.0.1!

I was also under the impression that the ping test is done every 60s or
120s so these tests just can't be true positive results. 
Poking around I also found that the test to my hobbit server (this is
127.0.0.1 mind you) went up in early December.

Looking for any input at this point!

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


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