It's a shell script, right? One of the first things I do with a failing
cron or other background script is to put at the top:
set -x
exec >/tmp/scriptname 2>&1
Then every run puts a trace in the /tmp file. If you don't get output,
it's not firing, if you do, it should show you exactly what happened.
On Wed, October 5, 2011 14:23, Knox, Wesley wrote:
This is a TCP listener I added to the bb-services file on the server. The
test is to telnet to the port expect an ok and if anything else comes thru
it goes yellow. I believe you are right about the underlying test not
running as these showed purple before I removed them with the drop
command. I will dig in and see if I can discover why these are not
testing. A manual telnet and other test I set up in the same fashion still
work so this is a bit boggling. Any suggestions as to how I can trouble
shoot xymon testing, is much appreciated as is the help given so far
-----Original Message-----
From: Elizabeth Schwartz [mailto:user-c61747246f66@xymon.invalid]
Sent: Sunday, October 02, 2011 7:05 PM
To: Knox, Wesley
Cc: xymon at xymon.com
Subject: Re: [Xymon] Re-add a dropped test
What test did you drop, and how is that test running - built-in on
client, built-in on server, or ext test or what?
You can force a status with bb like so:
/usr/local/xymon/server/bin/bb 127.0.0.1 "status server.example.com
mytest green" but that's just going to give you your dot back, it's not
going to solve your underlying problem.