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
misconfigured.
On Thu, Mar 21, 2019 at 10:38 AM John Thurston <user-ce4d79d99bab@xymon.invalid>
wrote:
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 XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
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?