EXT script showing critical in 1 hr when interval 7 days
I have created an 'ext' script that is set in the clientlaunch.cfg to run on an interval of 7 days "INTERVAL 7d"
After it has run, going GREEN as it should, in about 15 minutes it goes purple, and will go Red shortly thereafter. But it is not scheduled to run for 7 days.
I even tried putting an entry on the server-side: hobbit-clients.cfg: sysdb 8d
This to no avail.
What should I do to get it to only have this go red or purple if it fails on the next time it is run? It appears that every time the hobbit client reports, that it views this weekly scheduled event as a failure.
--
Shawn Saunders MIST Team member Jet Propulsion Laboratory 4800 Oak Grove Drive Pasadena, CA 91109 MS 230-310 Office: (818) 354-4667 / 230-310A Mobile: (818) 458-0789 FAX: (818) 393-9022
Any fool can make things bigger, more complex, and more violent. It takes a touch of genius-and a lot of courage-to move in the opposite direction. Albert Einstein
When you send your status message, use 'status+7d'.
The exact syntax is on the man page for the bb command.
Shawn Saunders wrote:
I have created an 'ext' script that is set in the clientlaunch.cfg to run on an interval of 7 days "INTERVAL 7d"
After it has run, going GREEN as it should, in about 15 minutes it goes purple, and will go Red shortly thereafter. But it is not scheduled to run for 7 days.
I even tried putting an entry on the server-side: hobbit-clients.cfg: sysdb 8d
This to no avail. What should I do to get it to only have this go red or purple if it fails on the next time it is run? It appears that every time the hobbit client reports, that it views this weekly scheduled event as a failure.
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007
participants (2)
-
rsmrcina＠wi.rr.com
-
shawn.saunders＠jpl.nasa.gov