Xymon Mailing List Archive search

Xymon 4.3.10 and "multi-source status" errors

5 messages in this thread

list Ryan Novosielski · Tue, 11 Dec 2012 12:55:50 -0500 ·
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My xymond test is often yellow, and near as I can tell, the reason is
often that I have so-called "multi-source statuses." However, the
"second" source is the Xymon server, and this appears to happen most
often when tests are disabled (as the blue status comes from the Xymon
server). Should I be ignoring this? Is there a misconfiguration
somewhere that has this server not properly identifying messages from
itself?

Thanks for your help.

- -- 
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDHc6YACgkQmb+gadEcsb6IRACfTH2APBg6vkSYdAd2FPfMKmUJ
aygAoL6HVCab1U2X+eIb/GSNYqZNcmCN
=754I
-----END PGP SIGNATURE-----
list Japheth Cleaver · Tue, 11 Dec 2012 12:22:36 -0800 (PST) ·
quoted from Ryan Novosielski
My xymond test is often yellow, and near as I can tell, the reason is
often that I have so-called "multi-source statuses." However, the
"second" source is the Xymon server, and this appears to happen most
often when tests are disabled (as the blue status comes from the Xymon
server). Should I be ignoring this? Is there a misconfiguration
somewhere that has this server not properly identifying messages from
itself?

Thanks for your help.
Not sure entirely what you're referring to here... Can you provide sample
output from the different tests?

-jc
list Ryan Novosielski · Tue, 11 Dec 2012 15:35:48 -0500 ·
quoted from Japheth Cleaver
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/11/2012 03:22 PM, user-87556346d4af@xymon.invalid wrote:
My xymond test is often yellow, and near as I can tell, the
reason is often that I have so-called "multi-source statuses."
However, the "second" source is the Xymon server, and this
appears to happen most often when tests are disabled (as the blue
status comes from the Xymon server). Should I be ignoring this?
Is there a misconfiguration somewhere that has this server not
properly identifying messages from itself?

Thanks for your help.
Not sure entirely what you're referring to here... Can you provide
sample output from the different tests?
If you click on the "xymond" dot, I get the following much of the way
down the page (you can see this on yours too, but it will be blank
most likely):

Multi-source statuses
  www-test.umdnj.edu:conn   reported by 10.32.5.120 and 130.219.XXX.XXX
  www-test.umdnj.edu:cpu    reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:disk   reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:files  reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:fma    reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:ftp    reported by 10.32.5.120 and 130.219.XXX.XXX
  www-test.umdnj.edu:memory reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:msgs   reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:ports  reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:procs  reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:raid   reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:telnet reported by 10.32.5.120 and 130.219.XXX.XXX
  www-test.umdnj.edu:temp   reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:vmio   reported by 10.32.5.120 and 10.32.5.106
  www-test.umdnj.edu:zfs    reported by 10.32.5.120 and 10.32.5.106

...(the former is the Xymon server) and I just figured out the
specific case that causes it. If you disable the server with
"$XYMONHOME/server/bin/xymon $XYMONDISP 'disable host.domain.com* 5m
Testing' etc. instead of using the GUI, you will see this. It appears
that doing it via the GUI does not result in this happening. Bug of
feature?
quoted from Ryan Novosielski

- -- 
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| |  | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDHmSAACgkQmb+gadEcsb70uACfYDsOaneBZ3I7sB9ZfPq/+xn/
DNMAnRYLXKtHBWcIBpQ9IGM56o4Nu3/w
=emGB
-----END PGP SIGNATURE-----
list Jeremy Laidman · Thu, 13 Dec 2012 13:03:50 +1100 ·
quoted from Ryan Novosielski
On 12 December 2012 07:35, Novosielski, Ryan <user-ae4522577e16@xymon.invalid> wrote:
specific case that causes it. If you disable the server with
"$XYMONHOME/server/bin/xymon $XYMONDISP 'disable host.domain.com* 5m
Testing' etc. instead of using the GUI, you will see this. It appears
that doing it via the GUI does not result in this happening. Bug of
feature?

Could it be caused by the GUI not using $XYMONDISP but instead using
$XYMSRV?  On my systems, $XYMONDISP is not even defined.  On yours, $XYMSRV
might be different to $XYMONDISP, and thus the reason for the different
behaviour.

J
list Ryan Novosielski · Wed, 12 Dec 2012 21:24:21 -0500 ·
I will look into all of these and see if they're correct or if I've misspoken. I'm guessing others do not see this behavior?
quoted from Jeremy Laidman


From: Jeremy Laidman [mailto:user-71895fb2e44c@xymon.invalid]
Sent: Wednesday, December 12, 2012 09:03 PM
To: Novosielski, Ryan
Cc: user-87556346d4af@xymon.invalid <user-87556346d4af@xymon.invalid>; xymon at xymon.com <xymon at xymon.com>
Subject: Re: [Xymon] Xymon 4.3.10 and "multi-source status" errors

On 12 December 2012 07:35, Novosielski, Ryan <user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid>> wrote:
specific case that causes it. If you disable the server with

"$XYMONHOME/server/bin/xymon $XYMONDISP 'disable host.domain.com<http://host.domain.com>* 5m
quoted from Jeremy Laidman
Testing' etc. instead of using the GUI, you will see this. It appears
that doing it via the GUI does not result in this happening. Bug of
feature?

Could it be caused by the GUI not using $XYMONDISP but instead using $XYMSRV?  On my systems, $XYMONDISP is not even defined.  On yours, $XYMSRV might be different to $XYMONDISP, and thus the reason for the different behaviour.

J