Invalid hour value. expected string/number value; 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 ” invalid hour value. expected string/number value; 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 “invalid hour value. expected string/number value; but found [{}]”classname  is DayTimes.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} catch (NumberFormatException nfe) {
 throw new ElasticsearchParseException("invalid time hour value [{}]"; value);
 } 
 default:
 throw new ElasticsearchParseException("invalid hour value. expected string/number value; but found [{}]"; token);
 }
 } 
 public static int parseMinuteValue(XContentParser parser; XContentParser.Token token) throws IOException; ElasticsearchParseException {
 switch (token) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content