Xymon Mailing List Archive search

is depends broken?

list Cami Sardinha
Thu, 12 Sep 2013 07:56:28 +0200
Message-Id: <CABvMvgQWWK1sJ1=F=user-6d80d4d19398@xymon.invalid>

Hey..

DEPENDS I haven't managed to get working properly, even with copy/paste
examples that have been posted to the list in the past (even for conn
tests!).
I'm looking forward to the overhaull of DEPENDS and ROUTE so that it no
longer relies on net-tests and moves things into the core (to include combo
tests) but least i heard there was no ETA on that.

Regards,
Cami


On Wed, Sep 11, 2013 at 8:58 PM, Troy Adams <user-81e3256385bc@xymon.invalid> wrote:
So I did a little testing with "route:".

The behavior I see when I test is (where "child" is the machine depended
on the "parent"):
By default (no route directive used here), when the child:conn and the
child:http both go red then the child:http is turned clear because of
innate dependency on conn.

With the route directive in place, when the parent:conn, child:conn and
the child:http all go red then the child:http is turned clear (same as
above) but the child:conn bounces between yellow and red (with an
approximate cycle of 1:30 red and 30s yellow).

Next when I bring up the parent:conn (restore ping function), the
child:conn goes red and stays red.

I guess the bottom line is, I can't get "route" or "depends" to do what I
want or even what the manual says they do.  Looks to me like something is
broken real bad.

I am using Xymon 4.3.10.

Anybody have a clue what to do?


cheers,

Troy


----- Original Message -----
From: "Troy Adams" <user-81e3256385bc@xymon.invalid>
To: "Josh Luthman" <user-4c45a83f15cb@xymon.invalid>
Cc: xymon at xymon.com
Sent: Thursday, August 22, 2013 11:26:22 AM GMT -07:00 US/Canada Mountain
Subject: Re: [Xymon] is depends broken?

Galen,

I should have also stated that google was up for the entire period (no
flapping).


Josh,

I take it, you mean replace my previous configuration where it said:
  depends=(http:google.com/http)
and make it:
  route:google.com
so it ends up as:
  XXX.XXX.XXX.XXX  www          # trace http://www route:google.com

I tried that and when I block both hosts google/icmp,http and www:http
with iptables they both show red, I was expecting www:http to show clear to
get the same functionality as "depends".

Any thoughts?


cheers,

Troy


----- Original Message -----
From: "Josh Luthman" <user-4c45a83f15cb@xymon.invalid>
To: "Galen Johnson" <user-87f955643e3d@xymon.invalid>
Cc: xymon at xymon.com, "Troy Adams" <user-81e3256385bc@xymon.invalid>
Sent: Monday, August 19, 2013 8:56:57 PM GMT -07:00 US/Canada Mountain
Subject: Re: [Xymon] is depends broken?

Use route:other.host.com

Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
On Aug 19, 2013 10:31 PM, "Galen Johnson" <user-87f955643e3d@xymon.invalid> wrote:
 #2 sounds a lot like "flapping".  Does "depends" honor flapping or
would a flapping server still show red?  Or am  I not understanding the
situation?

=G=

*From:* Xymon [xymon-bounces at xymon.com] on behalf of Troy Adams [
user-81e3256385bc@xymon.invalid]
*Sent:* Monday, August 19, 2013 5:34 PM
*To:* xymon
*Subject:* [Xymon] is depends broken?

   I have the following in my 'hosts.cfg':

209.85.225.105   google.com   # http://www.google.com
XXX.XXX.XXX.XXX  www          # trace http://www depends=(http:
google.com/http)


Yesterday, the web server (www) was down for 55 minutes.  The Xymon
record shows that:

   1. google.com/http was green for that whole period
   2. www/http bounced between red and clear for the whole period (with
   a bounce frequency of 5 minutes)
   3. My other Xymon server (configured without "depends") shows a solid
   55 minute outage (red for 55 minutes).

This behavior is not what I expect from reading the man page.

I tried to reproduce this problem with "depends" on my test Xymon server
and was able to confirm the same behavior.

Is there a workaround to this problem with my Xymon 4.3.10 server?


cheers,

Troy


This communication is intended for the use of the recipient to whom it is
addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or subsequent
reply, should be deleted or destroyed.