Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Linux/Unix Script Monitor - Testing on node : failed with 'NotAvailable' status - The script returned status code DOWN.

Linux/Unix Script Monitor - Testing on node ps-dev-web1: failed with 'NotAvailable' status - The script returned status code DOWN.

I'm new to Orion and I'm trying to figure out how to run Linux/Unix Scripts to monitor hosts.

I've been following the instructions from Solarwinds' site - Creating a Linux/Unix Script Monitor - to no avail.

So I set it up using the following:
   - I pick a server from the "Set Test Node" link
   - Component Type: Linux/Unix Script Monitor
   - Enabled Component: Yes
   - Credential for Monitoring: set to a user and pass with appropriate permissions
        - Port number: 22
   - Command Line: perl ${SCRIPT} /tmp/avail_mem.pl localhost
   - Script Working Directory: /tmp/
   - Script Body: I post the contents of my script here

I didn't post the contents of the scripts as it's a little lengthy. But needless to say, I've tested out this script remotely on the host and it runs just fine. It also returns the required Exit 0, 1 with "Message:" and "Statistics".

When I hit the "test" button I always see the following:

Can someone please point me in the right direction?

Thank you,

Franck

Find more posts tagged with

Accepted answers

All comments

jiri.tomek

Hello Franck,
your message means that script runs just fine but your exit code that is used for that particular run is 1. Check if you r script logic is correct and note that for UP you have to return 0 and for DOWN you have to return 1.

ffallateuf

Thank you for your response Jiri.

I did verify the script logic to be correct. In fact, I ran the script locally on the host before running it through Orion and it executes just fine, returning a 0 for UP and 1 for DOWN:

[ffallateuf@ps-dev-web1 /]$ perl /tmp/avail_mem.pl localhost
Message: Available memory at host "localhost": 768444 in kB
Statistic: 768444
[ffallateuf@ps-dev-web1 /]$ echo $?
0

Is there anyway to get any more debug output through ORION to correctly see what's going on? All I'm seeing is that it's DOWN, which is not possible as it runs just fine locally.

If I understand correctly, ORION SSHs remotely to the host and then executes the script from the local directory with the given command line + command line arguments, which in this case is correct.

Thank you,

Franck

jiri.tomek

APM creates script on target node and executes it there, not in local directory. If you create script test.sh that has body:

ls

and specify Script Working Directory to /tmp/, script is copied to /tmp/ on target node and executed there so it lists contents of /tmp/ of target node.

You can add debug statements to your script that will write debug messages to a file. Then you can get this file from target node and examine it.