: expected (at ) but found – 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 ” : expected (at ) but found ” 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 “: expected [{}] (at [{}]) but found [{}]”classname  is Intervals.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// char token
 if (token.ch != 0) {
 char found = string.charAt(startToken);
 if (found != token.ch) {
 throw new ParsingException(source; invalidIntervalMessage(string) + ": expected [{}] (at [{}]) but found [{}]";
 token.ch; startToken; found);
 }
 startToken++;
 }
 // number char

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content