Xymon server report purple because custom client script do not report often enough
list Kim Johansen
Hey,
I have made a script which count how many times a string appears in a log file. Nothing special. And it works fine.
Doing the testing of this script I made the interval to 1m, just so I did not have to wait to long to test changes.
Now that I finish with the script I want the interval, configured in clientlaunch.cfg, to run every 60m, so I have changed it in clientlaunch.cfg.
But that result in the xymon server is complaining about stop reporting from the client on this custom check.
I have tried to delete the test status from the server, but with no luck.
Is there something I have misunderstood and is there a way to fix it?
Clientlaunch.cfg
[razor-count]
ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
CMD $HOBBITCLIENTHOME/ext/razor-report-count.sh
LOGFILE /var/log/hobbit/razor-report-count.log
INTERVAL 60m
Thanks,
Kim.
list Scot Kreienkamp
Xymon expects results every 5-10 minutes or the test will turn purple to indicate no report has been received. If you really want it to run every 60 minutes you need to put something to indicate that in the test. In the text sent back to the server you have to put something like status+60m or something like that. Look in the xymon man pages for the exact syntax. Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | Office: XXX-XXX-XXXX | | Mobile: XXXXXXXXXX | Email: user-9678697f1438@xymon.invalid
-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Kim Johansen Sent: Friday, July 10, 2015 4:34 PM To: xymon at xymon.com Subject: [Xymon] Xymon server report purple because custom client script do not report often enough
▸
Hey,
I have made a script which count how many times a string appears in a
log file. Nothing special. And it works fine.
Doing the testing of this script I made the interval to 1m, just so I
did not have to wait to long to test changes.
Now that I finish with the script I want the interval, configured in
clientlaunch.cfg, to run every 60m, so I have changed it in
clientlaunch.cfg.
But that result in the xymon server is complaining about stop reporting
from the client on this custom check.
I have tried to delete the test status from the server, but with no luck.
Is there something I have misunderstood and is there a way to fix it?
Clientlaunch.cfg
[razor-count]
ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
CMD $HOBBITCLIENTHOME/ext/razor-report-count.sh
LOGFILE /var/log/hobbit/razor-report-count.log
INTERVAL 60m
Thanks,
Kim.
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
list Ralph Mitchell
You'll want to set the lifetime so that it spans several reporting intervals. The default interval is 5 minutes, with a lifetime of 30 minutes, so that multiple reports can be missed before it shows purple dots. With a 60 minute interval, you should set the lifetime to at least 120: status+120 Ralph Mitchell On Fri, Jul 10, 2015 at 4:51 PM, Scot Kreienkamp <
▸
user-9678697f1438@xymon.invalid> wrote:
Xymon expects results every 5-10 minutes or the test will turn purple to indicate no report has been received. If you really want it to run every 60 minutes you need to put something to indicate that in the test. In the text sent back to the server you have to put something like status+60m or something like that. Look in the xymon man pages for the exact syntax. Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | Office: XXX-XXX-XXXX | | Mobile: XXXXXXXXXX | Email: user-9678697f1438@xymon.invalid-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Kim Johansen Sent: Friday, July 10, 2015 4:34 PM To: xymon at xymon.com Subject: [Xymon] Xymon server report purple because custom client script do not report often enough Hey, I have made a script which count how many times a string appears in a log file. Nothing special. And it works fine. Doing the testing of this script I made the interval to 1m, just so I did not have to wait to long to test changes. Now that I finish with the script I want the interval, configured in clientlaunch.cfg, to run every 60m, so I have changed it in clientlaunch.cfg. But that result in the xymon server is complaining about stop reporting from the client on this custom check. I have tried to delete the test status from the server, but with no luck. Is there something I have misunderstood and is there a way to fix it? Clientlaunch.cfg [razor-count] ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg CMD $HOBBITCLIENTHOME/ext/razor-report-count.sh LOGFILE /var/log/hobbit/razor-report-count.log INTERVAL 60m Thanks, Kim.This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
list Kim Johansen
Thank you both, That was the part I have missed, now it is working fine. Have great day, Kim
▸
On 07/10/2015 11:04 PM, Ralph Mitchell wrote:You'll want to set the lifetime so that it spans several reporting intervals. The default interval is 5 minutes, with a lifetime of 30 minutes, so that multiple reports can be missed before it shows purple dots. With a 60 minute interval, you should set the lifetime to at least 120: status+120 Ralph Mitchell On Fri, Jul 10, 2015 at 4:51 PM, Scot Kreienkamp
<user-9678697f1438@xymon.invalid <mailto:user-9678697f1438@xymon.invalid>>
▸
wrote:
Xymon expects results every 5-10 minutes or the test will turn
purple to indicate no report has been received. If you really
want it to run every 60 minutes you need to put something to
indicate that in the test. In the text sent back to the server
you have to put something like status+60m or something like that.
Look in the xymon man pages for the exact syntax.
Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate
One La-Z-Boy Drive | Monroe, Michigan 48162 | Office:
XXX-XXX-XXXX <tel:XXX-XXX-XXXX> | | Mobile: XXXXXXXXXX
<tel:XXXXXXXXXX> | Email: user-9678697f1438@xymon.invalid▸
-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>] On Behalf Of KimJohansen Sent: Friday, July 10, 2015 4:34 PM
To: xymon at xymon.com <mailto:xymon at xymon.com>
▸
Subject: [Xymon] Xymon server report purple because custom client script do not report often enough Hey, I have made a script which count how many times a string appears in a log file. Nothing special. And it works fine. Doing the testing of this script I made the interval to 1m, just so I did not have to wait to long to test changes. Now that I finish with the script I want the interval, configured in clientlaunch.cfg, to run every 60m, so I have changed it in clientlaunch.cfg. But that result in the xymon server is complaining about stop reporting from the client on this custom check. I have tried to delete the test status from the server, but with no luck. Is there something I have misunderstood and is there a way to fix it? Clientlaunch.cfg [razor-count] ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg CMD $HOBBITCLIENTHOME/ext/razor-report-count.sh LOGFILE /var/log/hobbit/razor-report-count.log INTERVAL 60m Thanks, Kim.This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.