You enabled set -e
aka errexit
.
Your script will exit if one of the commands returns a non-zero exit code, and it may not always be obvious which command specifically fails:
- Some may print a helpful error identifying itself and the problem
- Some (like
wget
) may briefly mention an error way back in pagefuls of output - Some (like
grep
) may not show errors or any output at all, the script just exits
To know which command is causing a problem, run script with -x
aka xtrace
:
bash -x script.sh
Or add set -x
to the script itself:
set -x
set -e
...
This will cause the script to print out each command being executed, so you can see which one was the last.
If you would like to ignore the exit status of a command, you can add || true
:
# Causes exit if you lack read permission on any directory
find . -name '*.sh'
# Does not cause the script to exit
find . -name '*.sh' || true
If you would like to be alerted when set -e
would trigger in your script, you can set a trap:
#!/bin/bash
set -e
# Show error if commands exit with non-zero
trap 'ret=$?; echo "$0:$LINENO: Error: set -e triggered"; exit $ret' ERR
# Would have failed silently
grep doesnotexist /etc/passwd
echo "This does not run"
When executed:
$ ./foo
./foo:6: Error: set -e triggered