Output.toString(UTF-8).eachLine { line> logger.error(line) } – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Output.toString(UTF-8).eachLine { line> logger.error(line) } ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task.

Log Context

Log “output.toString(‘UTF-8’).eachLine { line -> logger.error(line) }” classname is LoggedExec.groovy.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             standardOutput = output
            errorOutput = output
            ignoreExitValue = true
            doLast {
                if (execResult.exitValue != 0) {
                    output.toString('UTF-8').eachLine { line -> logger.error(line) }
                    throw new GradleException("Process '${executable} ${args.join(' ')}' finished with non-zero exit value ${execResult.exitValue}")


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content