21 Mar
2019
21 Mar
'19
6:38 p.m.
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?