Log Running the cli with: ${command} – How To Solve Related Issues

Log 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 try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)


This guide will help you check for common problems that cause the log “Running the cli with: ${command}” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

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)


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Errors While Running The Elasticsea  

Try To Run Elasticsearch But Keeps  


About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now