custom script run interval
list Deepak Deore
I have a custom script setup on client side, which I want to run on every 24 hours and i don't want to change the default lifetime for other tests. Used below line but still after 30 mins it is going into purple. $BB $BBDISP "status+25h $MACHINE.$COLUMN $COLOR `date` `echo -e "Daily status: \ \n$(cat /tmp/status.log) "`"
list Paul Root
That should work. Works for me on many external scripts. $BB $BBDISP "status+1w $MACHINE.$TEST $COLOR `cat $StatusFile`"
▸
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of deepak deore
Sent: Friday, April 19, 2013 1:18 PM
To: xymon at xymon.com
Subject: [Xymon] custom script run interval
I have a custom script setup on client side, which I want to run on every 24 hours and i don't want to change the default lifetime for other tests.
Used below line but still after 30 mins it is going into purple.
$BB $BBDISP "status+25h $MACHINE.$COLUMN $COLOR `date` `echo -e "Daily status: \
\n$(cat /tmp/status.log) "`"
list Michael Beatty
Your syntax is correct, it should work. Maybe echo the statement to the log file to see what exactly it is sending. Is it possible that you are calling the statement from more than one location and the other location doesn't have the 25h lifetime? Michael Beatty
▸
On 04/19/2013 02:18 PM, deepak deore wrote:I have a custom script setup on client side, which I want to run on every 24 hours and i don't want to change the default lifetime for other tests. Used below line but still after 30 mins it is going into purple. $BB $BBDISP "status+25h $MACHINE.$COLUMN $COLOR `date` `echo -e "Daily status: \ \n$(cat /tmp/status.log) "`"
list Deepak Deore
for now i have setup below entry in clientlaunch.cfg, when i set it to 25h it goes purple, am I doing right? INTERVAL 25m On Sat, Apr 20, 2013 at 1:12 AM, Michael Beatty
▸
<user-4aea7c115850@xymon.invalid>wrote:
Your syntax is correct, it should work. Maybe echo the statement to the log file to see what exactly it is sending. Is it possible that you are calling the statement from more than one location and the other location doesn't have the 25h lifetime? Michael Beatty On 04/19/2013 02:18 PM, deepak deore wrote: I have a custom script setup on client side, which I want to run on every 24 hours and i don't want to change the default lifetime for other tests. Used below line but still after 30 mins it is going into purple. $BB $BBDISP "status+25h $MACHINE.$COLUMN $COLOR `date` `echo -e "Daily status: \ \n$(cat /tmp/status.log) "`"
Xymon mailing user-d459c9d661b6@xymon.invalid
list Michael Beatty
You are doing it right, it should work. Try disabling the alert in clientlaunch.cfg and sending the alert manually from the command line and see if it goes purple after 30 minutes? Michael Beatty
▸
On 04/20/2013 03:21 AM, deepak deore wrote:for now i have setup below entry in clientlaunch.cfg, when i set it to 25h it goes purple, am I doing right? INTERVAL 25m On Sat, Apr 20, 2013 at 1:12 AM, Michael Beatty <user-4aea7c115850@xymon.invalid <mailto:user-4aea7c115850@xymon.invalid>> wrote: Your syntax is correct, it should work. Maybe echo the statement to the log file to see what exactly it is sending. Is it possible that you are calling the statement from more than one location and the other location doesn't have the 25h lifetime? Michael Beatty On 04/19/2013 02:18 PM, deepak deore wrote:I have a custom script setup on client side, which I want to run on every 24 hours and i don't want to change the default lifetime for other tests. Used below line but still after 30 mins it is going into purple. $BB $BBDISP "status+25h $MACHINE.$COLUMN $COLOR `date` `echo -e "Daily status: \ \n$(cat /tmp/status.log) "`"
list Deepak Deore
Whenever I am confident about the configuration which doesn't work, then I restart xymon server. And which did the trick here :-) This is the 3rd time I restarted xymon server and it did the trick always if there are no problem with the configuration. So looks like xymon goes mad while the things are tested very frequently. On Mon, Apr 22, 2013 at 5:35 PM, Michael Beatty
▸
<user-4aea7c115850@xymon.invalid>wrote:
You are doing it right, it should work. Try disabling the alert in clientlaunch.cfg and sending the alert manually from the command line and see if it goes purple after 30 minutes? Michael Beatty On 04/20/2013 03:21 AM, deepak deore wrote: for now i have setup below entry in clientlaunch.cfg, when i set it to 25h it goes purple, am I doing right? INTERVAL 25m On Sat, Apr 20, 2013 at 1:12 AM, Michael Beatty < user-4aea7c115850@xymon.invalid> wrote:Your syntax is correct, it should work. Maybe echo the statement to the log file to see what exactly it is sending. Is it possible that you are calling the statement from more than one location and the other location doesn't have the 25h lifetime? Michael Beatty On 04/19/2013 02:18 PM, deepak deore wrote: I have a custom script setup on client side, which I want to run on every 24 hours and i don't want to change the default lifetime for other tests. Used below line but still after 30 mins it is going into purple. $BB $BBDISP "status+25h $MACHINE.$COLUMN $COLOR `date` `echo -e "Daily status: \ \n$(cat /tmp/status.log) "`" Xymon mailing user-d459c9d661b6@xymon.invalid
list Deepak Deore
and how do I set this custom script to run on a specific time? eg. I want to run it at 12:00 PM every day Right now it is running after 24 hours but not at the time I want,
▸
On Tue, Apr 23, 2013 at 7:52 PM, deepak deore <user-7b03b2a1ee70@xymon.invalid>wrote:
Whenever I am confident about the configuration which doesn't work, then I restart xymon server. And which did the trick here :-) This is the 3rd time I restarted xymon server and it did the trick always if there are no problem with the configuration. So looks like xymon goes mad while the things are tested very frequently. On Mon, Apr 22, 2013 at 5:35 PM, Michael Beatty < user-4aea7c115850@xymon.invalid> wrote:You are doing it right, it should work. Try disabling the alert in clientlaunch.cfg and sending the alert manually from the command line and see if it goes purple after 30 minutes? Michael Beatty On 04/20/2013 03:21 AM, deepak deore wrote: for now i have setup below entry in clientlaunch.cfg, when i set it to 25h it goes purple, am I doing right? INTERVAL 25m On Sat, Apr 20, 2013 at 1:12 AM, Michael Beatty < user-4aea7c115850@xymon.invalid> wrote:Your syntax is correct, it should work. Maybe echo the statement to the log file to see what exactly it is sending. Is it possible that you are calling the statement from more than one location and the other location doesn't have the 25h lifetime? Michael Beatty On 04/19/2013 02:18 PM, deepak deore wrote: I have a custom script setup on client side, which I want to run on every 24 hours and i don't want to change the default lifetime for other tests. Used below line but still after 30 mins it is going into purple. $BB $BBDISP "status+25h $MACHINE.$COLUMN $COLOR `date` `echo -e "Daily status: \ \n$(cat /tmp/status.log) "`" Xymon mailing user-d459c9d661b6@xymon.invalid
list Steve Holmes
▸
On Wed, Apr 24, 2013 at 1:04 PM, deepak deore <user-7b03b2a1ee70@xymon.invalid>wrote:
and how do I set this custom script to run on a specific time? eg. I want to run it at 12:00 PM every day Right now it is running after 24 hours but not at the time I want,
Use cron with xymoncmd instead of running out of clientlaunch.cfg. Steve
▸
On Tue, Apr 23, 2013 at 7:52 PM, deepak deore <user-7b03b2a1ee70@xymon.invalid>wrote:Whenever I am confident about the configuration which doesn't work, then I restart xymon server. And which did the trick here :-) This is the 3rd time I restarted xymon server and it did the trick always if there are no problem with the configuration. So looks like xymon goes mad while the things are tested very frequently. On Mon, Apr 22, 2013 at 5:35 PM, Michael Beatty < user-4aea7c115850@xymon.invalid> wrote:You are doing it right, it should work. Try disabling the alert in clientlaunch.cfg and sending the alert manually from the command line and see if it goes purple after 30 minutes? Michael Beatty On 04/20/2013 03:21 AM, deepak deore wrote: for now i have setup below entry in clientlaunch.cfg, when i set it to 25h it goes purple, am I doing right? INTERVAL 25m On Sat, Apr 20, 2013 at 1:12 AM, Michael Beatty < user-4aea7c115850@xymon.invalid> wrote:Your syntax is correct, it should work. Maybe echo the statement to the log file to see what exactly it is sending. Is it possible that you are calling the statement from more than one location and the other location doesn't have the 25h lifetime? Michael Beatty On 04/19/2013 02:18 PM, deepak deore wrote: I have a custom script setup on client side, which I want to run on every 24 hours and i don't want to change the default lifetime for other tests. Used below line but still after 30 mins it is going into purple. $BB $BBDISP "status+25h $MACHINE.$COLUMN $COLOR `date` `echo -e "Daily status: \ \n$(cat /tmp/status.log) "`" Xymon mailing user-d459c9d661b6@xymon.invalid
--
If they give you ruled paper, write the other way. -Juan Ramon Jimenez,
poet, Nobel Prize in literature (1881-1958)
I prayed for freedom for twenty years, but received no answer until I
prayed with my legs. -Frederick Douglass, Former slave, abolitionist,
editor, and orator (1817-1895)
list Larry Barber
Also the 'CRONDATE' entry for tasks.cfg:
The CRONDATE keyword is used for tasks that must run at regular intervals
or at a specific time. The time specification
is identical to the one used by cron in crontab(5) entries, i.e.
a sequence of numbers for minute, hour, day-of-month,
month and day-of-week. Three-letter abbreviations in english can be
used for the month and day-of-week fields. An aster-
isk is a wildcard. So in the example above, this job would run once
a month, at 4:30 AM on the 1st day of the month.
Thanks,
Larry Barber
▸
On Wed, Apr 24, 2013 at 12:14 PM, Steve Holmes <user-ec1bf77b1b44@xymon.invalid> wrote:
On Wed, Apr 24, 2013 at 1:04 PM, deepak deore <user-7b03b2a1ee70@xymon.invalid>wrote:and how do I set this custom script to run on a specific time? eg. I want to run it at 12:00 PM every day Right now it is running after 24 hours but not at the time I want,Use cron with xymoncmd instead of running out of clientlaunch.cfg. SteveOn Tue, Apr 23, 2013 at 7:52 PM, deepak deore <user-7b03b2a1ee70@xymon.invalid>wrote:Whenever I am confident about the configuration which doesn't work, then I restart xymon server. And which did the trick here :-) This is the 3rd time I restarted xymon server and it did the trick always if there are no problem with the configuration. So looks like xymon goes mad while the things are tested very frequently. On Mon, Apr 22, 2013 at 5:35 PM, Michael Beatty < user-4aea7c115850@xymon.invalid> wrote:You are doing it right, it should work. Try disabling the alert in clientlaunch.cfg and sending the alert manually from the command line and see if it goes purple after 30 minutes? Michael Beatty On 04/20/2013 03:21 AM, deepak deore wrote: for now i have setup below entry in clientlaunch.cfg, when i set it to 25h it goes purple, am I doing right? INTERVAL 25m On Sat, Apr 20, 2013 at 1:12 AM, Michael Beatty < user-4aea7c115850@xymon.invalid> wrote:Your syntax is correct, it should work. Maybe echo the statement to the log file to see what exactly it is sending. Is it possible that you are calling the statement from more than one location and the other location doesn't have the 25h lifetime? Michael Beatty On 04/19/2013 02:18 PM, deepak deore wrote: I have a custom script setup on client side, which I want to run on every 24 hours and i don't want to change the default lifetime for other tests. Used below line but still after 30 mins it is going into purple. $BB $BBDISP "status+25h $MACHINE.$COLUMN $COLOR `date` `echo -e "Daily status: \ \n$(cat /tmp/status.log) "`" Xymon mailing user-d459c9d661b6@xymon.invalid-- If they give you ruled paper, write the other way. -Juan Ramon Jimenez, poet, Nobel Prize in literature (1881-1958) I prayed for freedom for twenty years, but received no answer until I prayed with my legs. -Frederick Douglass, Former slave, abolitionist, editor, and orator (1817-1895)