Failed to parse action /. unexpected token / – Elasticsearch Error How To Solve Related Issues



Failed to parse action /. unexpected token / – 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 “failed to parse action /. unexpected token /” 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”failed to parse [{}] action [{}/{}]. unexpected token [{}/{}]”classname  is JiraAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} catch (Exception e) {
  throw new ElasticsearchParseException("failed to parse [{}] action [{}/{}]. failed to parse [{}] field"; e; TYPE;
  watchId; actionId; Field.FIELDS.getPreferredName());
  }
  } else {
  throw new ElasticsearchParseException("failed to parse [{}] action [{}/{}]. unexpected token [{}/{}]"; TYPE; watchId;
  actionId; token; currentFieldName);
  }
  }
  if (fields == null) {
  fields = Collections.emptyMap();

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 Parsing JSON giving "unexpected token o" error -views 688,787 ,score 451

SyntaxError: Unexpected token o in JSON at position 1 -views   325,683,score 125



Find Configuration Errors

Analyze Now