[SOLVED] Bash: handling an exit code

robcar · 07-07-2015, 05:06 AM

Hello,
I'm writing a bash script to keep ethernet switch counters under control via SNMP queries.
At some point this script connects via snmpwalk:

Code:

# Get array port index
arrIndex=(`snmpwalk -v 2c -c $community $switchIpAddr $etherStatsEntry.1 | awk '{print $4;}'`)

# Is it possibile to get answers from switch?
# The exit state of the last command is evaluated '0' if True or '1' if False and is intercepted by '$?'
if [ $? -ne 0 ]; then
   # Something's wrong
   echo "Wrong IP address or SNMP not configured for switch."
   exit $EXIT_UNKNOWN
fi

If the switch IP is wrong or if SNMP on the switch is not configured I got:

Code:

Timeout: No Response from 10.68.254.245

How can I handle this exception in the script?
The code above doesn't work, because I always get '0' exit code.
I noticed that:

Quote:

arrIndex=(`snmpwalk -v 2c -c $community $switchIpAddr $etherStatsEntry.1 | awk '{print $4;}'`)

and

Quote:

snmpwalk -v 2c -c $community $switchIpAddr $etherStatsEntry.1 | awk '{print $4;}'

exit with '0'.

Only

Code:

snmpwalk -v 2c -c $community $switchIpAddr $etherStatsEntry.1

exits with '1' in case the IP is wrong.

I would prefer not to do a pre-flight check by repeating the command snmpwalk, because that would take extra time.

So the question is: how can I handle the exit code generated by the command snmpwalk above, which is then piped and then assigned to an array?

Thanks.
--
rob

chrism01 · 07-07-2015, 05:30 AM

1. instead of

Code:

(` .. `)

use

Code:

$( ..)

More readable.

2. As you've noticed, if you chain cmds together you get the exit code of the last cmd run (makes sense when you think about it).
Save the result of the first cmd and test the exit code and/or check the o/p text.

robcar · 07-07-2015, 05:58 AM

Quote:

Originally Posted by chrism01

2. As you've noticed, if you chain cmds together you get the exit code of the last cmd run (makes sense when you think about it).
Save the result of the first cmd and test the exit code and/or check the o/p text.

Thanks,
actually I solved by prepending

Code:

set -o pipefail

at the beginning of the script and it seems to be working fine

Quote:

"If pipefail is enabled, the pipeline’s return status is the value of the last (rightmost) command to exit with a non-zero status, or zero if all commands exit successfully."