Linux Script Monitor Return Value

I've created an Application Monitor Template using the Linux/Unix Script Monitor.

According to the help, I report my application status via the exit code:

linux.monitor.return.codes.png

When my application is up and I return 0, everything is good and my application shows as Up.

If my script returns a 1 as in the above table, The application is shown as Down which is what I want:

But when I go to Application Details, an error message in red is displayed that indicates that there was a failure because the return code was non zero.

This also occurs if I return a 2, 3, or other non zero value. The app status correctly shows Warning, Critical or Unknown but I get a red error message in the details page.

bad.return.png

How can I use the script return code to show Application status AND not have that error message? It confuses the operators.

This shows my script command line and script body for testing

thanks

Find more posts tagged with

linux script

sam 6.2.2

Accepted answers

All comments

xtraspecialj

You ever get this figured out? I'd like to use the Exit Codes for my script and stumbled upon this post whilst researching it.

roadster

No, this has not been resolved.

I opened a SolarWinds help ticket and we traded numerous emails.

They were able to duplicate this on their system and ended up saying don't return non-zero values from scripts to set node state and that I should use threshold values instead.

I replied ok, how should I do that?

And they responded with the very same doc I referenced in my post above showing how to return non-zero values to set node state.

aparna.valsala

In the last exit, do not do a exit $status, rather return a numeric value, something like exit(0) or exit(1), let me know if that worked.

roadster

Hi -

Thanks for your suggestion. $status is a numeric value. It is the end result of the script's calculation if the application is up/down/warning/unknown.

Using either $status or a direct number like 0 or 1 does "work", the Node shows the application in the desired state up/down/warning/unknown.

The problem is that is if exit is any number other then 0, the application details page will show the annoying and misleading message:

So as a test, this script "works" and shows the application up

And this script also "works" and shows the application as down but also shows that error message:

bad.return.png

ralfs

Hi,

which kind of return code you send when you get that error? Because I use in my Unix Shell/Perl and also in the Powershell scripts return codes and it works perfectly if I use exit codes 0,1,2,3 .

Kind regards,

Ralf

equalswql

Hello roadster,

I have the same issue where when exiting with 1 I get the same message. ralfs can you please share what it is you are doing that is letting you avoid that error? And what version of SAM / Orion core you are using? It seems to me like although the script is exiting correctly, it is almost as if solarwinds isn't supporting the exit code of 1 (I say so only because of the error message).

Thank you,

equalswql