Xymon Mailing List Archive search

"noconn" configuration feature oddity ...

4 messages in this thread

list Ian Diddams · Mon, 5 Oct 2020 11:53:01 +0000 (UTC) ·
A colleague and I noticed a feature of xymon last week, and tested it across a few version from 4.3.12 to 4.3.17?? [ upgrading etc etc is not a trivial matter in these environments so its meaningless to just suggest "upgrade asap" - although see [1] for general feedback etc ].

If a new host is added to hosts.cfg with a noconn configuration in a new group or page configuratiopn

eg


page test Test
group-compress <H3>Test</H3>
4.5.6.7 test #? noconn

that server NEVER appears in the webpage as expected, although the new group does appear albeit then empty

If it is introduced without that noconn parementer then it does as expected appear.? Then adding noconn to it subsequently does indeed drop the conn column and reproting then continues as normal.


We have also found that specifying noping instead of noconn does include the server in the webpage with a white face in the conn column - ie it does get included, so is maybe a work round? at least) 
However...

 adding 
4.5.6.7 test #? noconn 
to an already existing group/page - that server DOES get listed but with no subsequent tests against it - the line remains empty
This would appear to be a feature of xymon Ive not come accrioss in 9+ years of using it.? 
[1] Anybody found any other "fixes" to be ablwe to sepcify noconn from the outset?

I've googled but nothing appears to match that - though that could just be my rubbish googling skills... 

UPDATE:? deeper wierdness...? if i add a eg ssh test to that hosts.cfg line ...? then the server DOES get added...? 
cheers
ian
list Jeremy Laidman · Tue, 6 Oct 2020 10:44:41 +1100 ·
Ian

An interesting discovery indeed. Although I'm not greatly surprised. A host
that has no tests and has never had any test results, is not a particularly
interesting one, and is rather like a tree falling in an uninhabited
forest, where nobody knows - or even cares - about the state of the tree.
I'd attribute this phenomenon to the type of "undefined behaviour" that can
occur when any process is asked to do something it wasn't designed to do
and which, in essence, makes no sense.

Unless I'm missing something.

Cheers
Jeremy


On Mon, 5 Oct 2020 at 23:33, Ian Diddams via Xymon <xymon at xymon.com> wrote:
---------- Forwarded message ----------
From: Ian Diddams <user-7fbf34ed5219@xymon.invalid>
To: "xymon at xymon.com" <xymon at xymon.com>
Cc:
Bcc:
Date: Mon, 5 Oct 2020 11:53:01 +0000 (UTC)
Subject: "noconn" configuration feature oddity ...
quoted from Ian Diddams
A colleague and I noticed a feature of xymon last week, and tested it
across a few version from 4.3.12 to 4.3.17   [ upgrading etc etc is not a
trivial matter in these environments so its meaningless to just suggest
"upgrade asap" - although see [1] for general feedback etc ].

If a new host is added to hosts.cfg with a noconn configuration in a new
group or page configuratiopn

eg


page test Test
group-compress <H3>Test</H3>
4.5.6.7 test #  noconn

that server NEVER appears in the webpage as expected, although the new
group does appear albeit then empty

If it is introduced without that noconn parementer then it does as
expected appear.  Then adding noconn to it subsequently does indeed drop
the conn column and reproting then continues as normal.


We have also found that specifying noping instead of noconn does include
the server in the webpage with a white face in the conn column - ie it does
get included, so is maybe a work round  at least)

However...

adding

4.5.6.7 test #  noconn

to an already existing group/page - that server DOES get listed but with
no subsequent tests against it - the line remains empty

This would appear to be a feature of xymon Ive not come accrioss in 9+
years of using it.

[1] Anybody found any other "fixes" to be ablwe to sepcify noconn from the
outset?

I've googled but nothing appears to match that - though that could just be
my rubbish googling skills...


UPDATE:  deeper wierdness...  if i add a eg ssh test to that hosts.cfg
line ...  then the server DOES get added...

cheers

ian


---------- Forwarded message ----------
From: Ian Diddams via Xymon <xymon at xymon.com>
To: "xymon at xymon.com" <xymon at xymon.com>
Cc:
Bcc:
Date: Mon, 5 Oct 2020 11:53:01 +0000 (UTC)
Subject: [Xymon] "noconn" configuration feature oddity ...

list Ralph Mitchell · Mon, 5 Oct 2020 22:21:16 -0400 ·
Jeremy,
I think he's saying that a host which starts off like that *never* shows
up, even when it starts generating real status messages.

Ian,
Are there any entries in the ghost list?  Or error messages in the logs
when the real status messages start coming in and get dropped/ignored?

The good news is, I just tried to reproduce that behaviour in 4.3.30, and
the host shows up just fine.  So, I assume whatever goes wrong is fixed
somewhere later than 4.3.17.

Ralph Mitchell
quoted from Jeremy Laidman


On Mon, Oct 5, 2020 at 7:44 PM Jeremy Laidman <user-0608abae5e7c@xymon.invalid> wrote:
Ian

An interesting discovery indeed. Although I'm not greatly surprised. A
host that has no tests and has never had any test results, is not a
particularly interesting one, and is rather like a tree falling in an
uninhabited forest, where nobody knows - or even cares - about the state of
the tree. I'd attribute this phenomenon to the type of "undefined
behaviour" that can occur when any process is asked to do something it
wasn't designed to do and which, in essence, makes no sense.

Unless I'm missing something.

Cheers
Jeremy


On Mon, 5 Oct 2020 at 23:33, Ian Diddams via Xymon <xymon at xymon.com>
wrote:
---------- Forwarded message ----------
From: Ian Diddams <user-7fbf34ed5219@xymon.invalid>
To: "xymon at xymon.com" <xymon at xymon.com>
Cc:
Bcc:
Date: Mon, 5 Oct 2020 11:53:01 +0000 (UTC)
Subject: "noconn" configuration feature oddity ...
A colleague and I noticed a feature of xymon last week, and tested it
across a few version from 4.3.12 to 4.3.17   [ upgrading etc etc is not a
trivial matter in these environments so its meaningless to just suggest
"upgrade asap" - although see [1] for general feedback etc ].

If a new host is added to hosts.cfg with a noconn configuration in a new
group or page configuratiopn

eg


page test Test
group-compress <H3>Test</H3>
4.5.6.7 test #  noconn

that server NEVER appears in the webpage as expected, although the new
group does appear albeit then empty

If it is introduced without that noconn parementer then it does as
expected appear.  Then adding noconn to it subsequently does indeed drop
the conn column and reproting then continues as normal.


We have also found that specifying noping instead of noconn does include
the server in the webpage with a white face in the conn column - ie it does
get included, so is maybe a work round  at least)

However...

adding

4.5.6.7 test #  noconn

to an already existing group/page - that server DOES get listed but with
no subsequent tests against it - the line remains empty

This would appear to be a feature of xymon Ive not come accrioss in 9+
years of using it.

[1] Anybody found any other "fixes" to be ablwe to sepcify noconn from
the outset?

I've googled but nothing appears to match that - though that could just
be my rubbish googling skills...


UPDATE:  deeper wierdness...  if i add a eg ssh test to that hosts.cfg
line ...  then the server DOES get added...

cheers

ian


---------- Forwarded message ----------
From: Ian Diddams via Xymon <xymon at xymon.com>
To: "xymon at xymon.com" <xymon at xymon.com>
Cc:
Bcc:
Date: Mon, 5 Oct 2020 11:53:01 +0000 (UTC)
Subject: [Xymon] "noconn" configuration feature oddity ...

list Ian Diddams · Tue, 6 Oct 2020 10:35:13 +0000 (UTC) ·
Jeremy,>>>I think he's saying that a host which starts off like that *never* shows up, even when it starts generating real status messages.? 
CORRECT
Ian,>>>Are there any entries in the ghost list?? Or error messages in the logs when the real status messages start coming in and get dropped/ignored?
NONE :-(? (I did look but that's a good consideration)
The good news is, I just tried to reproduce that behaviour in 4.3.30, and the host shows up just fine.? So, I assume whatever goes wrong is fixed somewhere later than 4.3.17.
THANKS :-)

cheers
ian