On Wed, Nov 09, 2005 at 12:49:57PM -0500, Steve wrote:
I wrote a client script to monitor an application, added to the clientlaunch.cfg file restarted hobbit, the monitor works well
Because the application I am monitoring is faulty I added to the client script a section of code to start up the application should it fail. I shut down the application and Hobbit starts it up ... Cool.
To avoid having the application start up during the backup or maintenance window I disable the client script.
I ran a test backup to be sure it worked, but it appears that Hobbit executes the client script even when the test is disabled, and the application goes from blue to red to green.
You're right that Hobbit runs the client script regardless of whether the status that the script reports is disabled or not. hobbitlaunch
which runs the script simply has no idea what status column(s) your script might report.
So now the 64K question ... what can I change so the test does not run when disabled or ... where did I error?
Have your script check if the test is disabled, and abort if it is. Something like this:
STATUS=`$BB $BBDISP "query $MACHINE.mytest" | awk '{print $1}'`
if [ "$STATUS" = "blue" ]; then exit 0; fi
The bb(1) man-page has some more examples of how you can use the "query"
command.
Regards,
Henrik