Extend timers to avoid purples
list Kevin Hanrahan
Can anybody tell me how to get a test to avoid purples if it is only run once a day? Thanks Note: The information contained in this email and in any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. The recipient should check this email and any attachments for the presence of viruses. Sender accepts no liability for any damages caused by any virus transmitted by this email. If you have received this email in error, please notify us immediately by replying to the message and delete the email from your computer. This e-mail is and any response to it will be unencrypted and, therefore, potentially unsecure. Thank you. NOVA Information Systems, Inc.
list Paul Williamson
In the bb world, there is a "touchtime" utility that would put a date/time stamp on a file in the future by x minutes. I'm sure it would work fine for your needs, but Hobbit may have something built in. Paul
user-fd47fec4b039@xymon.invalid 06/24/05 3:49 PM >>>
▸
Can anybody tell me how to get a test to avoid purples if it is only run once a day? Thanks Note: The information contained in this email and in any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. The recipient should check this email and any attachments for the presence of viruses. Sender accepts no liability for any damages caused by any virus transmitted by this email. If you have received this email in error, please notify us immediately by replying to the message and delete the email from your computer. This e-mail is and any response to it will be unencrypted and, therefore, potentially unsecure. Thank you. NOVA Information Systems, Inc.
list Andy France
Hi Kevin, Kevin Hanrahan wrote on 25/06/2005 07:49:42:
▸
Can anybody tell me how to get a test to avoid purples if it is only run once a day? Thanks
As Hobbit doesn't have it's own client (yet!), I'll assume it understands all of the standard bb client options. I haven't tested it yet as I'm in the process of integrating our daily backup scripts into hobbit, where I too will need this feature. If you read the help pages on the bb4.org site, you'll run across this one... http://demo.bb4.com/bb/help/help/status_message_format.htm When you call the bb client executable from your script, change "status" to "status+1440" in the message header for the lifetime to be 24 hours. You might want to bump it to 25 hours to cope with those times your daily process takes a little bit longer ;-) HTH, Andy. ##################################################################################### This email is intended for the person to whom it is addressed only. If you are not the intended recipient, do not read, copy or use the contents in any way. The opinions expressed may not necessarily reflect those of ZESPRI Group of Companies ('ZESPRI'). While every effort has been made to verify the information contained herein, ZESPRI does not make any representations as to the accuracy of the information or to the performance of any data, information or the products mentioned herein. ZESPRI will not accept liability for any losses, damage or consequence, however, resulting directly or indirectly from the use of this e-mail/attachments. #####################################################################################
list Kevin Grady
You're assumption is right.
▸
On 6/24/05, Andy France <user-ee2a9e4eaf57@xymon.invalid> wrote:Hi Kevin, Kevin Hanrahan wrote on 25/06/2005 07:49:42:Can anybody tell me how to get a test to avoid purples if it is only run once a day? ThanksAs Hobbit doesn't have it's own client (yet!), I'll assume it understands all of the standard bb client options. I haven't tested it yet as I'm in the process of integrating our daily backup scripts into hobbit, where I too will need this feature. If you read the help pages on the bb4.org site, you'll run across this one... http://demo.bb4.com/bb/help/help/status_message_format.htm When you call the bb client executable from your script, change "status" to "status+1440" in the message header for the lifetime to be 24 hours. You might want to bump it to 25 hours to cope with those times your daily process takes a little bit longer ;-) HTH, Andy. ##################################################################################### This email is intended for the person to whom it is addressed only. If you are not the intended recipient, do not read, copy or use the contents in any way. The opinions expressed may not necessarily reflect those of ZESPRI Group of Companies ('ZESPRI'). While every effort has been made to verify the information contained herein, ZESPRI does not make any representations as to the accuracy of the information or to the performance of any data, information or the products mentioned herein. ZESPRI will not accept liability for any losses, damage or consequence, however, resulting directly or indirectly from the use of this e-mail/attachments. #####################################################################################
list Henrik Størner
▸
On Sat, Jun 25, 2005 at 01:59:45PM +1200, Andy France wrote:
Kevin Hanrahan wrote on 25/06/2005 07:49:42:Can anybody tell me how to get a test to avoid purples if it is only run once a day? ThanksAs Hobbit doesn't have it's own client (yet!), I'll assume it understands all of the standard bb client options. If you read the help pages on the bb4.org site
Or do a "man bb". Except I hadn't gotten around to describing the full syntax of the status command. It's in there now.
▸
When you call the bb client executable from your script, change "status" to "status+1440" in the message header for the lifetime to be 24 hours.
Hobbit also accepts "status+25h" Regards, Henrik
list Gee Pee
If you mean: I run a test once a day and it turns purple after 30 minutes, then you should extend the validity of the result of the test. This defaults to 30 minutes and can be extended on the BB- client-side, see: http://bb4.org/bb/help/bb-man.html#6.9 Peter Op 24-jun-2005, om 21:49 heeft user-fd47fec4b039@xymon.invalid het volgende geschreven:
▸
Can anybody tell me how to get a test to avoid purples if it is only run once a day? Thanks Note: The information contained in this email and in any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. The recipient should check this email and any attachments for the presence of viruses. Sender accepts no liability for any damages caused by any virus transmitted by this email. If you have received this email in error, please notify us immediately by replying to the message and delete the email from your computer. This e-mail is and any response to it will be unencrypted and, therefore, potentially unsecure. Thank you. NOVA Information Systems, Inc.
list Sladewig
▸
On 06/25/2005 06:18 AM, Gee Pee wrote:
If you mean: I run a test once a day and it turns purple after 30 minutes, then you should extend the validity of the result of the test. This defaults to 30 minutes and can be extended on the BB- client-side, see: http://bb4.org/bb/help/bb-man.html#6.9
I also have experienced problems similar to this. I have a external script on the client which I was running with a half hour as its time. When I switched to hobbit I began to get purple and recovered messages every 30 minutes from each client. The recovered message would be timestamped the exact time or +1sec from the purple. I ended up having to change the client to run every 5 minutes and still ocassionally I get purple/recovered. Perhaps a little fudge factor is needed to allow time for the client to complete the script. Something like status time plus and extra 30 seconds. -- steve
▸
Op 24-jun-2005, om 21:49 heeft user-fd47fec4b039@xymon.invalid het volgende geschreven:Can anybody tell me how to get a test to avoid purples if it is only run once a day? Thanks
list Adam Goryachev
▸
On Mon, 2005-06-27 at 07:21 -0500, sladewig wrote:
On 06/25/2005 06:18 AM, Gee Pee wrote:If you mean: I run a test once a day and it turns purple after 30 > minutes, then you should extend the validity of the result of the > test. This defaults to 30 minutes and can be extended on the BB- > client-side, see: http://bb4.org/bb/help/bb-man.html#6.9I also have experienced problems similar to this. I have a external script on the client which I was running with a half hour as its time. When I switched to hobbit I began to get purple and recovered messages every 30 minutes from each client. The recovered message would be timestamped the exact time or +1sec from the purple. I ended up having to change the client to run every 5 minutes and still ocassionally I get purple/recovered. Perhaps a little fudge factor is needed to allow time for the client to complete the script. Something like status time plus and extra 30 seconds.
When you consider that the default is to send a report every 5 minutes, but turn purple after 30 minutes, you should see that there is definitely some room for delays being allowed for. For something checking hourly, I would suggest a fudge facter of 2 hours and 20 minutes. Of course, you also need to consider how long that test might not run for without you finding out about it. PS, AFAIK, hobbit will run tests exactly when due, while BB doesn't (well, more recent versions try to, but probably don't excactly match up). Regards, Adam
list Kevin Hanrahan
OK, ...thanks for the reply... I tried that, I think.
I made a custom script for checking domain registration expiration dates and
I am calling it from hobbitlaunch as such:
[Domain Registration]
CMD /home/hobbit/server/ext/ext-domainname.sh
INTERVAL 1400m
I am passing the status of the test (using an allready existing BB test)
like this:
# Get Status proc - used to get all responses
#
get_status()
{
DaysLeft=`$PROBE $1`
RESULT="OK: Remaining days - $DaysLeft"
COLOR="green"
if [ "$DaysLeft" != "Record not found" ]
then
if [ "$DaysLeft" -le "$DAYSLEFTWARN" ]
then
RESULT="WARNING: Remaining days - $DaysLeft"
COLOR="yellow"
fi
if [ "$DaysLeft" -le "$DAYSLEFTERROR" ]
then
RESULT="ERROR: Remaining days - $DaysLeft"
COLOR="red"
fi
else
RESULT="ERROR: $DaysLeft"
COLOR="red"
fi
echo "$COLOR+1430m `date` $RESULT"
}
# Main body
$GREP "$TEST" $BBHOSTS |
while read line; do
TESTNAME=`echo "$line" | awk '{print $2}'`
STATUS=`get_status $TESTNAME`
if [ ! -z "$STATUS" ]
then
# NOW USE THE BB COMMAND TO SEND THE DATA ACROSS
SDISPLAY="status $TESTNAME.$TEST $STATUS"
echo "$SDISPLAY" >> /tmp/ext-domainname.output
$BB $BBDISP "$SDISPLAY"
fi
done
After 30 minutes it always goes purple! I thought I was adding 1430 minutes
to the result time...am I wrong?
I am no coder so please be patient but I could use some direction here
please.
Thank you
kevin
▸
-----Original Message-----
From: user-ce4a2c883f75@xymon.invalid [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: Saturday, June 25, 2005 2:16 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Extend timers to avoid purples
On Sat, Jun 25, 2005 at 01:59:45PM +1200, Andy France wrote:Kevin Hanrahan wrote on 25/06/2005 07:49:42:Can anybody tell me how to get a test to avoid purples if it is only run once a day? ThanksAs Hobbit doesn't have it's own client (yet!), I'll assume it understands all of the standard bb client options. If you read the help pages on the bb4.org site
Or do a "man bb". Except I hadn't gotten around to describing the full syntax of the status command. It's in there now.
When you call the bb client executable from your script, change "status" to "status+1440" in the message header for the lifetime to be 24 hours.
Hobbit also accepts "status+25h" Regards, Henrik Note: The information contained in this email and in any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. The recipient should check this email and any attachments for the presence of viruses. Sender accepts no liability for any damages caused by any virus transmitted by this email. If you have received this email in error, please notify us immediately by replying to the message and delete the email from your computer. This e-mail is and any response to it will be unencrypted and, therefore, potentially unsecure. Thank you. NOVA Information Systems, Inc.
list Andy France
Kevin Hanrahan wrote on 28/06/2005 08:03:49:
▸
OK, ...thanks for the reply... I tried that, I think.
I made a custom script for checking domain registration expiration dates
and
I am calling it from hobbitlaunch as such:
[Domain Registration]
CMD /home/hobbit/server/ext/ext-domainname.sh
INTERVAL 1400m
I am passing the status of the test (using an allready existing BB test)
like this:
# Get Status proc - used to get all responses
#
get_status()
{
DaysLeft=`$PROBE $1`
RESULT="OK: Remaining days - $DaysLeft"
COLOR="green"
if [ "$DaysLeft" != "Record not found" ]
then
if [ "$DaysLeft" -le "$DAYSLEFTWARN" ]
then
RESULT="WARNING: Remaining days - $DaysLeft"
COLOR="yellow"
fi
if [ "$DaysLeft" -le "$DAYSLEFTERROR" ]
then
RESULT="ERROR: Remaining days - $DaysLeft"
COLOR="red"
fi
else
RESULT="ERROR: $DaysLeft"
COLOR="red"
fi
echo "$COLOR+1430m `date` $RESULT"
}
You shouldn't be adding the status lifetime to color...
echo "$COLOR `date` $RESULT"
▸
# Main body
$GREP "$TEST" $BBHOSTS |
while read line; do
TESTNAME=`echo "$line" | awk '{print $2}'`
STATUS=`get_status $TESTNAME`
if [ ! -z "$STATUS" ]
then
# NOW USE THE BB COMMAND TO SEND THE DATA ACROSS
SDISPLAY="status $TESTNAME.$TEST $STATUS"
echo "$SDISPLAY" >> /tmp/ext-domainname.output
$BB $BBDISP "$SDISPLAY"
fi
done
...you should be adding it here to status!
SDISPLAY="status+1430 $TESTNAME.$TEST $STATUS"
▸
After 30 minutes it always goes purple! I thought I was adding 1430 minutes to the result time...am I wrong? I am no coder so please be patient but I could use some direction here please. Thank you kevin
HTH! Andy.
▸
-----Original Message----- From: henrik Sent: Saturday, June 25, 2005 2:16 AM To: user-ae9b8668bcde@xymon.invalid Subject: Re: [hobbit] Extend timers to avoid purples
On Sat, Jun 25, 2005 at 01:59:45PM +1200, Andy France wrote:Kevin Hanrahan wrote on 25/06/2005 07:49:42:Can anybody tell me how to get a test to avoid purples if it is only run once a day? ThanksAs Hobbit doesn't have it's own client (yet!), I'll assume it understands all of the standard bb client options. If you read the help pages on the bb4.org site
Or do a "man bb".
Except I hadn't gotten around to describing the full syntax of the status command. It's in there now.
When you call the bb client executable from your script, change "status" to "status+1440" in the message header for the lifetime to be 24 hours.
Hobbit also accepts "status+25h"
Regards, Henrik
#####################################################################################
This email is intended for the person to whom it is addressed
only. If you are not the intended recipient, do not read, copy
or use the contents in any way. The opinions expressed may not
necessarily reflect those of ZESPRI Group of Companies ('ZESPRI').
While every effort has been made to verify the information
contained herein, ZESPRI does not make any representations
as to the accuracy of the information or to the performance
of any data, information or the products mentioned herein.
ZESPRI will not accept liability for any losses, damage or
consequence, however, resulting directly or indirectly from
the use of this e-mail/attachments.
#####################################################################################