Could not parse time. expected string/number value or an object; but found – How to solve this Elasticsearch error

Could not parse time. expected string/number value or an object; 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 Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” could not parse time. expected string/number value or an object; but found ” 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”could not parse time. expected string/number value or an object; but found [{}]”classname  is DayTimes.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public static DayTimes parse(XContentParser parser; XContentParser.Token token) throws IOException; ElasticsearchParseException {
  if (token == XContentParser.Token.VALUE_STRING) {
  return DayTimes.parse(parser.text());
  }
  if (token != XContentParser.Token.START_OBJECT) {
  throw new ElasticsearchParseException("could not parse time. expected string/number value or an object; but found [{}]"; token);
  }
  List hours = new ArrayList();
  List minutes = new ArrayList();
  String currentFieldName = null;
  while ((token = parser.nextToken()) != XContentParser.Token.END_OBJECT) {

 

Run the Check-Up to get a customized report like this:

Analyze your cluster