Running the cli with: ${command} – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Running the cli with: ${command} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Running the cli with: ${command}” classname is build.gradle.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         List command = [new File(project.runtimeJavaHome; 'bin/java').absolutePath]
        if ('true'.equals(System.getProperty('debug'; 'false'))) {
        command += '-agentlib:jdwp=transport=dt_socket;server=y;suspend=y;address=8000'
        }
        command += ['-jar'; jar.archivePath.absolutePath]
        logger.info("running the cli with: ${command}")

        new ProcessBuilder(command)
            .redirectOutput(ProcessBuilder.Redirect.INHERIT)
            .redirectInput(ProcessBuilder.Redirect.INHERIT)
            .redirectError(ProcessBuilder.Redirect.INHERIT)




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content