Can't identify dynamic column definitions from script output - Linux BASH Script

ANYTHING i put into a Linux script SAM component gives me the error "Can't identify dynamic column definitions from script output".

Below is a very simple script to test port availability against an IP. Does anyone know what i did wrong? Im starting with a simple script to try to bypass this error message.

This script works locally on the host as expected.

#!/bin/bash

#

tst="blank"

 

# test if port is available

if echo | nc -v 10.X.X.X 8009; then

  tst="it is up"

else

  tst="it is down"

fi

 

printf "Message.${tst}\n"

printf "Statistic.1"

exit 0

Find more posts tagged with

linux_script

sam monitoring

Accepted answers

All comments

shuth

The Linux script component monitor is expecting a Statistic output with optional corresponding Message.

So you may output Statistic and Message, or Statistic.1, Statistic.2, Message.1, Message.2, etc. if you need to output multiple fields/statistics.

https://documentation.solarwinds.com/en/success_center/sam/content/sam-linux-unix-script-monitor-sw3260.htm

I'm not 100% across the scripting itself but in your example you could return something like:

if echo | nc -v 10.X.X.X 8009; then
Statistic = 0
Message = "it is up"
Exit 0

else
Statistic = 1
Message = "it is down"
Exit 1

You can also use exit codes to have the component return a specific status.

https://documentation.solarwinds.com/en/success_center/sam/content/sam-script-report-status-through-exit-codes.htm

shuth

Found the article I was originally trying to add in:
documentation.solarwinds.com/.../sam-script-text-output.htm

acurrent

Hello, thank you so much for the response. I do have a stat and message value as well as an exit code in my script at the bottom (you must scroll down in the code window to see it).

Does the script you pasted above, with an actual IP added, work in your environment?

shuth

Ahh I didn't see the scroll down. As I said, I'm not 100% across the scripting side of things but I threw the following together and it tests OK in SAM.

#!/bin/bash

# test if port is available

if echo | nc -v x.x.x.x XXXX; then
 printf "Statistic: 0\n"
 printf "Message: it is up\n"
 exit 0
else
 printf "Statistic: 1\n"
 printf "Message: it is down\n"
 exit 0
fi

Does take a while to run the command but it eventually spits out a result. If I use a working IP/port the script hangs but I think it's waiting for something from your command. Even running the script manually it just sits there with "Connection to x.x.x.x XXXX port succeeded!"

Looking at your original script you could probably get it working by modifying it to something like below. But ideally you would modify the Statistic to be a number that differentiates between good/bad or maybe a response time or something.

printf "Statistic: 0\n"
printf "Message: ${tst}\n"