[Xymon] False procs alert

Walter Rutherford wlrutherford at alaska.edu
Thu Mar 21 19:46:23 CET 2019

Thank you John! That's far more possible causes than I thought of. C seems
the most
likely culprit since there is a second system with a similar name (a clone)
on the same
network. I also can't Remote Console that other system so it might be

On Thu, Mar 21, 2019 at 10:38 AM John Thurston <john.thurston at alaska.gov>

> Since the 'conn' test is normally populated by a server-side instance of
> xymonnet, I can think of a few ways this could happen:
> A) DNS round-robin (multiple A-records), one of which isn't responding
> B) More than one instance of xymonnet running, one of which is on a
> network which is firewalled from the host
> C) An errant client sending a 'status' message with the 'conn' tag
> D) Multipathing on your network, one path of which isn't working
> --
>     Do things because you should, not just because you can.
> John Thurston    907-465-8591
> John.Thurston at alaska.gov
> Department of Administration
> State of Alaska
> On 3/21/2019 10:25 AM, Walter Rutherford wrote:
> > So now it's mostly a curiosity. Has anyone else seen a system report
> > flapping like this?
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20190321/b1a28a2a/attachment.html>

More information about the Xymon mailing list