Why error handling prevents silent failures in Bash Scripting - Challenge Your Understanding

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output when a command fails without error handling?

Consider this bash script snippet:

#!/bin/bash
mkdir /root/testdir
 echo "Directory created"

What will be the output when run as a normal user without root privileges?

Bash Scripting

#!/bin/bash
mkdir /root/testdir
 echo "Directory created"

A No output at all

B Directory created

C mkdir: cannot create directory ‘/root/testdir’: Permission denied

D

mkdir: cannot create directory ‘/root/testdir’: Permission denied
Directory created

💡 Hint

Think about what happens when mkdir fails but the script continues.

Without error handling, the mkdir command fails and prints an error to stderr, but the script continues and prints 'Directory created'. This can mislead users into thinking the directory was created successfully.

🧠 Conceptual

intermediate

Why use 'set -e' in bash scripts?

What is the main effect of adding set -e at the start of a bash script?

A It makes the script exit immediately if any command returns a non-zero status.

B It runs the script in debug mode.

C It prints all commands before executing them.

D It ignores all errors and continues running the script.

💡 Hint

Think about how to stop a script when something goes wrong.

set -e causes the script to stop running as soon as any command fails, preventing silent failures and unexpected behavior.

🔧 Debug

advanced

Identify the error handling problem in this script

What is wrong with the error handling in this bash script?

#!/bin/bash
cp /source/file.txt /dest/
if [ $? -eq 0 ]; then
  echo "Copy succeeded"
else
  echo "Copy failed"
fi
rm /source/file.txt

Bash Scripting

#!/bin/bash
cp /source/file.txt /dest/
if [ $? -eq 0 ]; then
  echo "Copy succeeded"
else
  echo "Copy failed"
fi
rm /source/file.txt

A The script uses $? incorrectly to check the command status.

B The script does not check if /dest/ exists before copying.

C The script deletes the source file even if the copy failed, causing data loss.

D The script should use double brackets [[ ]] instead of single brackets [ ].

💡 Hint

Look at what happens after the copy command regardless of success.

The script removes the source file even if the copy failed, which can cause data loss. Proper error handling should prevent deleting the source if the copy did not succeed.

🚀 Application

advanced

How to handle errors in a pipeline to avoid silent failures?

Given this pipeline:

cat file.txt | grep 'pattern' | sort > output.txt

Which approach ensures the script detects if any command in the pipeline fails?

A Check only the exit status of the last command <code>sort</code>.

B Use <code>set -o pipefail</code> before running the pipeline.

C Add <code>|| exit 1</code> after the pipeline.

D Redirect errors to /dev/null to hide them.

💡 Hint

By default, bash only returns the last command's status in a pipeline.

set -o pipefail makes the pipeline return a failure status if any command fails, preventing silent failures in pipelines.

🧠 Conceptual

expert

Why is explicit error handling better than ignoring errors in automation scripts?

In automation scripts, why is it important to handle errors explicitly rather than ignoring them?

A Explicit error handling helps detect problems early and prevents cascading failures.

B Ignoring errors makes scripts run faster and more efficiently.

C Errors are rare and usually do not affect automation outcomes.

D Explicit error handling is only needed for interactive scripts, not automation.

💡 Hint

Think about what happens if a script continues after a failure unnoticed.

Handling errors explicitly ensures the script stops or reacts properly when something goes wrong, avoiding bigger issues later and making debugging easier.