I did something recently that checks the status of the conn column for
a host before running a custom script.
I accomplished it using hobbitdboard
BBJUNK=`bb localhost "hobbitdboard host=${BBHOST} test=ssh fields=color"`
if [[ "$BBJUNK" =~ "green" ]]; then
debugmsg Launching - $BBIP $BBHOST $SSHPRIV $BBJUNK;
nohup /usr/lib/hobbit/server/ext/pd2a.sh $BBIP $BBHOST $SSHPRIV &
elif [[ "$BBJUNK" == "" ]]; then
debugmsg Launching - $BBIP $BBHOST $SSHPRIV $BBJUNK;
nohup /usr/lib/hobbit/server/ext/pd2a.sh $BBIP $BBHOST $SSHPRIV &
else
outputmsg ssh down - $BBJUNK
fi
Maybe that's something you can adapt for your test?
On Wed, Dec 30, 2009 at 11:34 AM, Jerald Sheets <user-96a6f34c5806@xymon.invalid> wrote:I'm about to undertake writing a series of monitors for a custom app we have
here in-house.
This app lives over a networked filesystem (think cvfs or gpfs) that is
managed by two master nodes, a master and a failover. As a result, only one
node at a time can answer the query I want to give it.
My conundrum:
If I make the query form my Xymon server on node1 and it fails over to
node2, node1 becomes completely unable to answer the question, and that
check would go "red". Same for node2 back to node1.
If I run the check locally on each system, while one is working, the other
will go "blue".
Have any of you ever written monitors for servers that carry a service in an
active/passive configuration, and been able to keep the individual servers
from going into some strange state as a result of failovers and such?
How did you handle it?
---
Jerald M. Sheets jr.