Unable to parse – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” unable to parse ” 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 “unable to parse [“classname  is ManualTrigger.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return builder.startObject().endObject();
 static ManualTrigger parse(XContentParser parser) throws IOException{
 if (parser.currentToken() != XContentParser.Token.START_OBJECT){
 throw new ElasticsearchParseException("unable to parse [" + ManualTriggerEngine.TYPE +
 "] trigger. expected a start object token; found [" + parser.currentToken() + "]");
 XContentParser.Token token = parser.nextToken();
 if (token != XContentParser.Token.END_OBJECT) {
 throw new ElasticsearchParseException("unable to parse [" + ManualTriggerEngine.TYPE +


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content