bbwincmd.exe status+[time] does not seem to work as intended?
Hi there,
I've been trying to setup a test I call 'alive', which sends out a green signal every 1 minute, with a keep-alive time of 2 minutes.
This means, that if the server stops sending this signal twice, there will be a purple status.
Well, in theory anyway. I have not been able to get this working properly.
I use the following:
bbwincmd.exe [xymon server] status+2m [hostname] alive green "Last signal received at %time% on %date%"
This does send a green status every minute, but when I manually stop the script from being executed, the status becomes grey instead of purple.
Any suggestions would be most appreciated.
Kind regards,
Joost Hillen System Administrator Draads bv.
bbwincmd.exe [xymon server] status+2m [hostname] alive green "Last signal received at %time% on %date%"
This does send a green status every minute, but when I manually stop the script from being executed, the status becomes grey instead of purple.
It should go purple, unless you have the host configured with the "dialup" keyword in hosts.cfg, or if you are ping'ing it and the "conn" status is red. If the latter case, then you can add "noclear" in hosts.cfg:
noclear
Controls whether stale status messages go purple or clear
when a
host is down. Normally, when a host is down the client
statuses
("cpu", "disk", "memory" etc) will stop updating -
this would
usually make them go "purple" which can trigger alerts.
To avoid
that, Xymon checks if the "conn" test has failed, and if
that is
true then the other tests will go "clear" instead of
purple so
you only get alerts for the "conn" test. If you do
want the
stale statuses to go purple, you can use the "noclear"
tag to
override this behaviour.
Regards, Henrik
<henrik at ...> writes:
Thank you kindly - this seems to have done the trick, in combination with me fixing a syntax error (status+2m turned out to be wrong).
participants (2)
-
henrik@hswn.dk
-
jhillen@draads.nl