Redirect Stderr To Stdout For Piping

Redirects stderr to stdout to facilitate easier piping of error messages to other commands.

Terminal

<command1> 2>&1 | <command2>

<command1> 2>&1 | <command2>

#!/bin/bash

# Redirect Stderr To Stdout For Piping
{{command1}} 2>&1 | {{command2}}

When To Use

When debugging a process that outputs to stderr, and you want to capture all output in a single pipeline.

Pro Tip

Utilize 'set -o pipefail' to ensure that errors are caught in the pipeline correctly.

Command Builder

Tune the command before you copy it

Generated Command

<command1> 2>&1 | <command2>

Anatomy of Output

ERROR: Could not resolve all dependencies for configuration ':classpath'. Error Message

A critical error indicating dependency resolution failure.

FAILURE: Build failed with an exception. Build Status

Indicates the failure point.

* What went wrong: Failure Context

Describes the nature of the failure.

Troubleshooting

bash: command1: command not found

Solution: Ensure that command1 is installed and available in your PATH.

command2: No such file or directory

Solution: Ensure that command2 exists and is spelled correctly.

Invalid redirection: 2>&1

Solution: Check your redirection syntax for errors; ensure proper use of symbols.

Command Breakdown

<command1>: Base Command; The executable that performs this operation. Here it runs Command1 before the shell applies any redirect operators.
<command1>: command1; The value supplied for command1.
<command2>: command2; The value supplied for command2.

Alternative Approaches

Alternative filesystem tools for the same job.