Could not parse action / – Elasticsearch Error How To Solve Related Issues



Could not parse action / – 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 “could not parse action /” 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 (free tool that requires no installation). 

Log Context

Log”could not parse [{}] action [{}/{}]”classname  is EmailAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

password = WatcherXContentParser.secretOrNull(parser);
  } else if (Field.PROFILE.match(currentFieldName; parser.getDeprecationHandler())) {
  try {
  profile = Profile.resolve(parser.text());
  } catch (IllegalArgumentException iae) {
  throw new ElasticsearchParseException("could not parse [{}] action [{}/{}]"; TYPE; watchId; actionId; iae);
  }
  } else {
  throw new ElasticsearchParseException("could not parse [{}] action [{}/{}]. unexpected string field [{}]"; TYPE;
  watchId; actionId; currentFieldName);
  }

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 elasticsearch watcher could not parse search input -views 1,296 ,score 1

Watcher: [parse_exception] could not parse action [slack_test …  



Find Configuration Errors

Analyze Now