All -
For some reason many (all?) hosts are currently impervious to being disabled from the CLI if I use the "*" wildcard for the TESTNAME value. According to the xymon man page, I should be able "...To disable all tests for a host, use an asterisk "*" for TESTNAME." All tests for this host should go "blue" and stay in this state indefinitely (right?). However, I see this (timestamps in the prompts):
16:51:39 dwru002:/var/log/xymon> ~/xymon/server/bin/xymon $XYMON_server "disable twau009.* -1 "
16:52:16 dwru002:/var/log/xymon> ~/xymon/server/bin/xymon $XYMON_server "xymondboard host=twau009 fields=testname,color,disabletime"
trends|green|0
info|green|0
memory|blue|-1
files|blue|-1
msgs|blue|-1
ports|blue|-1
procs|blue|-1
disk|blue|-1
cpu|blue|-1
prtdiag|blue|-1
nfs|blue|-1
raid|blue|-1
tm|blue|-1
conn|blue|-1
sar|blue|-1
iostat2|blue|-1
then, about one minute later, I see my first "rebel" test ("conn") flip itself back to non-disabled:
16:53:14 dwru002:/var/log/xymon> ~/xymon/server//bin/xymon $XYMON_server "xymondboard host=twau009 fields=testname,color,disabletime" | grep -v blue
trends|green|0
info|green|0
conn|green|0
It takes about five-six minutes, but all eventually desert their "blue" status and return to green.
On the other hand, naming tests explicitly like the following seems to do the job more permanently:
17:03:50 dwru002:/var/log/xymon> ~/xymon/server/bin/xymon $XYMON_server "disable twau009.msgs -1 "
17:05:22 dwru002:/var/log/xymon> ~/xymon/server/bin/xymon $XYMON_server "disable twau009.files -1 "
17:05:28 dwru002:/var/log/xymon> ~/xymon/server/bin/xymon $XYMON_server "disable twau009.ports -1 "
Help?
~~~~~~~~~~~~~~~~~~~
David Mills
Systems Administrator
Northrop Grumman
XXX-XXX-XXXX
user-eb64c112f0e9@xymon.invalid