Xymon Mailing List Archive search

How to restore a check that was previously disabled

4 messages in this thread

list Alex Krumm-Heller · Wed, 15 Jan 2014 14:33:52 +1100 ·
Hi,

I am using xymon 4.3.12. I previously had the ports check disabled in the
hosts.cfg file using the defaults like:

0.0.0.0		.default.		# NOCOLUMNS=ports

I have then subsequently removed this NOCOLUMNS entry for ports and have
defined a check for a couple of servers straight from the example in the
man page to check for SSH port being open.

The check has not reappeared in the xymon webpage and was wondering if
there was anything special I need to do to "reactivate" it so xymon is
aware that it should appear again on the webpage?

Thanks

Alex
list Ryan Novosielski · Tue, 14 Jan 2014 22:45:00 -0500 ·
You realize that ports is a client-side test, right? Do you have a client running on that machine, etc.?
quoted from Alex Krumm-Heller


From: Alex Krumm-Heller [mailto:user-c1526349a4ef@xymon.invalid]
Sent: Tuesday, January 14, 2014 10:33 PM
To: xymon at xymon.com <xymon at xymon.com>
Subject: [Xymon] How to restore a check that was previously disabled

Hi,

I am using xymon 4.3.12. I previously had the ports check disabled in the hosts.cfg file using the defaults like:


0.0.0.0         .default.               # NOCOLUMNS=ports


I have then subsequently removed this NOCOLUMNS entry for ports and have defined a check for a couple of servers straight from the example in the man page to check for SSH port being open.

The check has not reappeared in the xymon webpage and was wondering if there was anything special I need to do to "reactivate" it so xymon is aware that it should appear again on the webpage?

Thanks

Alex
list Alex Krumm-Heller · Wed, 15 Jan 2014 19:03:37 +1100 ·
Yes I do. When I check the full info coming from the hosts I do see the
ports section in there with the full list of sockets. What I can't seem to
get working is the display on the server and the subsequent filtering based
on the rules I have denied.
quoted from Ryan Novosielski

On Wednesday, January 15, 2014, Novosielski, Ryan wrote:
You realize that ports is a client-side test, right? Do you have a client
running on that machine, etc.?


 *From*: Alex Krumm-Heller [mailto:user-c1526349a4ef@xymon.invalid <javascript:_e({},
'cvml', 'user-c1526349a4ef@xymon.invalid');>]
*Sent*: Tuesday, January 14, 2014 10:33 PM
*To*: xymon at xymon.com <javascript:_e({}, 'cvml', 'xymon at xymon.com');> <
xymon at xymon.com <javascript:_e({}, 'cvml', 'xymon at xymon.com');>>
quoted from Ryan Novosielski
*Subject*: [Xymon] How to restore a check that was previously disabled

Hi,

I am using xymon 4.3.12. I previously had the ports check disabled in the
hosts.cfg file using the defaults like:

0.0.0.0		.default.		# NOCOLUMNS=ports

I have then subsequently removed this NOCOLUMNS entry for ports and have
defined a check for a couple of servers straight from the example in the
man page to check for SSH port being open.

The check has not reappeared in the xymon webpage and was wondering if
there was anything special I need to do to "reactivate" it so xymon is
aware that it should appear again on the webpage?

Thanks

Alex
list Henrik Størner · Wed, 15 Jan 2014 09:27:58 +0100 ·
quoted from Alex Krumm-Heller
 

Den 15.01.2014 04:33, Alex Krumm-Heller skrev: 
I am using xymon
4.3.12. I previously had the ports check disabled in the hosts.cfg file
using the defaults like:
0.0.0.0 .default. # NOCOLUMNS=ports

I
have then subsequently removed this NOCOLUMNS entry for ports and have
defined a check for a couple of servers straight from the example in the
man page to check for SSH port being open.

The check has not
reappeared in the xymon webpage and was wondering if there was anything
special I need to do to "reactivate" it so xymon is aware that it should
appear again on the webpage?

Thanks

Alex
It should show up
automatically. Do you get anything from a 

xymon 127.0.0.1 "xymondboard
host=<hostname> test=ports" 

If you do, then the status exists - it
just doesn't show up on the webpage. Then the problem is with xymongen
not reading the correct configuration. Try "kill -HUP `pidof xymond`" to
force it to reload the configuration. 

If there is no ports-status
data, then it is xymond_client that doesn't generate it. Try "kill -HUP
`pidof xymond_client`" to force a reload of the configuration.


Regards,
Henrik