If the device status of the probe is Okay, then it means that InterMapper 
received an exit code of 0 from the command-line executing the probe.

You may be able to suss out what's happening by turning on detailed logging for 
Command-line Probes and Notifiers and looking at the debug log to see more 
precisely what InterMapper is executing and what's being returned. Info on 
doing this is here:

http://forums.dartware.com/viewtopic.php?t=866

If that doesn't help, please feel free to open a ticket at [email protected] 
with this info, and we'll do our best to help.

Thanks.

-- Christopher


mahrob wrote:
> Hi Jon,
> 
> Thanks for the input. The probe I have created to use this script has the
> command-exit block similar to the one you have listed:
> 
> <command-exit>
> down: ${EXIT_CODE} = 4
> critical: ${EXIT_CODE} = 3
> alarm: ${EXIT_CODE} = 2
> warning: ${EXIT_CODE} = 1
> okay: ${EXIT_CODE} = 0
> </command-exit>
> 
> But still the device status is in Okay state.
> 
> -Noman A.
> 
> On Thu, Jun 2, 2011 at 3:33 AM, Myers, Jon W <[email protected]>wrote:
> 
> 
> > not sure if list posts make it back to forum... but heres what I have for
> > an Senao access point, which uses commandline probe.
> > In the probe itself:
> > 
> > <command-exit>
> > down:${EXIT_CODE}=2
> > alarm:${EXIT_CODE}=1
> > okay:${EXIT_CODE}=0
> > </command-exit>
> > 
> > and in the commandline script output:
> > \{ $Name:="ConstTrailer"; $M:="00:02:6F:3A:92:9A"; $S:="AHRehab"; $C:="11";
> > $A:="0" }
> > 
> > the script (which happens to use php) uses "exit (0);" if everything is ok.
> > 
> > I've not gone so far as to report why there is an error if there is one,
> > and maybe thats the part that you really wanted to know.  But otherwise, the
> > icon will be green, orange or red depending on the return value.
> > 
> > ________________________________________
> > From: [email protected] [
> > [email protected]] On Behalf Of mahrob [
> > [email protected]]
> > Sent: Wednesday, June 01, 2011 10:37 AM
> > To: [email protected]; [email protected]
> > Subject: [IM-Talk] Need help on custom command-line probe
> > 
> > Hi All,
> > We have recently started using Intermapper for our Amazon cloud instances.
> > I have created a custom command-line probe to monitor disk usage on various
> > EC2 instances.  I have created probe and set it properly for the device to
> > be monitored. When I run the script in command line from the Intermapper
> > server, I get the proper stdout as follows:
> > 
> > "\{ $addr := "host-ip", $low_partition := "partition" } Running low on disk
> > space."
> > 
> > I have tested the exit code as well, which is 1, device status Alarming in
> > my probe. But the Intermapper is not taking the output. Can anyone point me
> > to the possible cause of Intermapper not setting the device status properly?
> > It would be really great help.
> > 
> > Thanks
> > Noman A.
> > 
> > 
> > -------------------- m2f --------------------
> > 
> > Read this topic online here:
> > http://forums.dartware.com/viewtopic.php?p=3451#3451
> > 
> > 
> > 
> > 
> > 
> > ____________________________________________________________________
> > List archives:
> > http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
> > To unsubscribe: send email to: [email protected]
> > 
> > ____________________________________________________________________
> > List archives:
> > http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
> > To unsubscribe: send email to: [email protected]
> > 
> > 
> > 
> ____________________________________________________________________
> List archives: 
> http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
> To unsubscribe: send email to: [email protected]
> 
>  Post generated using Mail2Forum (http://www.mail2forum.com)



-------------------- m2f --------------------

Read this topic online here:
http://forums.dartware.com/viewtopic.php?p=3471#3471





____________________________________________________________________
List archives: 
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [email protected]

Reply via email to