I was briefly able to reproduce a similar situation. However when I restarted
the server to investigate in more detail,
the situation had corrected itself. :(
It looks like there might be a problem with a dynamic reload of the probe while
the server is running. Please increment
the version number of your probe (in the <header> section) and reload probes
again.
When you have multiple down thresholds, like in your example above, the exit
code 2 will be mapped to unknown. The down
threshold is assigned to the exit code 1, since it is later in the list.
Please let me know if this helps,
Bill Fisher
Dartware, LLC
[EMAIL PROTECTED] wrote:
> This is the exit code section in our probe:
> <command-exit>
> critical:${EXIT_CODE}=6
> alarm:${EXIT_CODE}=5
> warning:${EXIT_CODE}=4
> okay:${EXIT_CODE}=3
> down:${EXIT_CODE}=2
> down:${EXIT_CODE}=1
> up:${EXIT_CODE}=0
> </command-exit>
>
> It is not working as expected. The only exit codes it recognizes is 0 and 1.
> Everything else causes a ? icon.
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
