Linux – How to check the exit status of several piped commands

As piping in bash commands is common and very usefull, controling the exit status of each piped commands in bash scripting can be vital, especially for backups.

I was checking by a customer the backups of a critical MySQL instance and was surprised even stunned that the return status of all of them was always  successfull when tested but physically on disk, the dumps were all empty.
No valid backups since a long time meaning no possible recovery.
Oups! How can it be?
I immediately opened the backup script with “vi” and had a look to the used statement which was the following:
1
mysqldump -u $USERNAME -p $PASS $DBNAME | bzip2 -9c -c > Dump.sql.gz
Now, what if the backup failed and the bzip2 command succeeded?
In fact, the exit status will be the one of the last command.
1
2
echo $?
0

And this will be always successfull.

So, the  solution to check the exit status of a particular command in piped commands is to use an inbuilt linux variable called  PIPESTATUS.
PIPESTATUS is an array variable which contain the exit status of every piped commands.
In our case,
echo ${PIPESTATUS[0]} will refer to the backup  and will be greater than 0 if it fails
echo ${PIPESTATUS[1]} will refer to the compression
echo ${PIPESTATUS[*]} or echo ${PIPESTATUS[@]} will give you the status of both.
So, one solution in our example could be:
1
2
3
4
5
6
7
8
mysqldump -u $USERNAME -p $PASS $DBNAME | bzip2 -9c -c > Dump.sql.gz
 
if [ ${PIPESTATUS[0]} -ne "0" ]
then
    echo "the MySQL Database backup failed with Error: ${PIPESTATUS[0]}";
else
    echo "The MySQL Database backup was successfull!";
fi
0 (0)
Article Rating (No Votes)
Rate this article
Attachments
There are no attachments for this article.
Comments
There are no comments for this article. Be the first to post a comment.
Full Name
Email Address
Security Code Security Code
Related Articles RSS Feed
linux unix aix banner /etc/issue
Viewed 2070 times since Fri, Aug 3, 2018
BIND for the Small LAN
Viewed 3496 times since Sun, May 20, 2018
LVM: Remove an existing Volume Group
Viewed 5465 times since Sat, Jun 2, 2018
Tip: SSD and Linux. Enable TRIM and check if it works
Viewed 17148 times since Fri, May 15, 2020
RHEL: Crash kernel dumps configuration and analysis on RHEL 7
Viewed 7226 times since Sat, Jun 2, 2018
RHCS6: Install a two-node basic cluster
Viewed 3505 times since Sun, Jun 3, 2018
How to Analyze or Read OS Watcher Output in three easy steps -- With Example ?
Viewed 41897 times since Thu, Jun 21, 2018
RHCS: Configure an active/backup pacemaker cluster
Viewed 9071 times since Sun, Jun 3, 2018
Top 20 OpenSSH Server Best Security Practices ssh linux aix
Viewed 6066 times since Fri, May 15, 2020
RHEL: Crash kernel dumps configuration and analysis on RHEL 6
Viewed 4900 times since Sat, Jun 2, 2018