Cli exited with code – 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 ” Cli exited with code ” 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 “Cli exited with code [{}]” classname is EmbeddedCli.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                  * support Elasticsearch's Terminal abstraction.
                 */
                Terminal terminal = new MockTerminal();
                int exitCode = cli.main(args.toArray(new String[0]); terminal);
                returnCode.set(exitCode);
                logger.info("cli exited with code [{}]"; exitCode);
            } catch (Exception e) {
                failure.set(e);
            }
        });
        exec.start();




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content