Xymon Mailing List Archive search

Xymon 4.3.10 and "multi-source status" errors

list Ryan Novosielski
Tue, 11 Dec 2012 15:35:48 -0500
Message-Id: <user-f3be2463decd@xymon.invalid>

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

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