No commands – Elasticsearch Error How To Solve Related Issues

No commands – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 errors 


This guide will help you check for common problems that cause the log “No commands” 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: routing, allocation, cluster.

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 (free tool that requires no installation). 

Log Context

Log”No commands”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public static AllocationCommands fromXContent(XContentParser parser) throws IOException {
  AllocationCommands commands = new AllocationCommands();
  XContentParser.Token token = parser.currentToken();
  if (token == null) {
  throw new ElasticsearchParseException("No commands");
  if (token == XContentParser.Token.FIELD_NAME) {
  if (!parser.currentName().equals("commands")) {
  throw new ElasticsearchParseException("expected field name to be named [commands]; got [{}] instead"; parser.currentName());

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 Installing elasticsearch docker image fails on command not found -views 556 

Dockerfile: not able to run bin command ubuntu -views   473,score 1

Find Configuration Errors

Analyze Now