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 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 ” 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.

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]"running the cli with: ${command}")

        new ProcessBuilder(command)


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content