CODEWITHSUNDEEP
bashscriptingpipeerror-reporting
Requist
Requist

Reputation: 165

How to pipe all terminal output including error messages from script to a log file

I am trying to make a readable log file for a large backupscript.
Within the script I simply pipe all output from the commands to a big file which then later can be "cleaned" by the script. For example:

echo "Error occurred" >> log.file
mount disk >> log.file

The warnings and error I have missed I pipe at the console when executing the script. 

backup.script >> log.file

But even than, error messages are not always logged in my file, when executing the script (with pipe) by cron I get mails from rsync and script errors:

rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: write failed on "/mnt/backup1/xxxxx": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9]
rsync: connection unexpectedly closed (215 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]

and when a script error occurs:

/data/scripts/backup.auto: line 320: syntax error near unexpected token `else'

How can I include these error messages in my log file?

Upvotes: 4

Views: 21690

Answers (1)

fredtantini
fredtantini

Reputation: 16556

To redirect STDERR to STDOUT, you have to add 2>&1 at the end of each line

echo "Error occurred" >> log.file 2>&1
mount disk >> log.file 2>&1

If you have multiple file descriptor, just redirect all of them to stdout 3>&1…

Edit: when I don't remember how file descriptors work, I go to http://www.tldp.org/LDP/abs/html/io-redirection.html

Upvotes: 13

Related Questions