Invalid time minute value (possible values may be between 0 and 59 incl.) – 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 time minute value (possible values may be between 0 and 59 incl.) ” 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 time minute value [{}] (possible values may be between 0 and 59 incl.)”classname  is DayTimes.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public static int parseMinuteValue(XContentParser parser; XContentParser.Token token) throws IOException; ElasticsearchParseException {
 switch (token) {
 case VALUE_NUMBER:
 int minute = parser.intValue();
 if (!DayTimes.validMinute(minute)) {
 throw new ElasticsearchParseException("invalid time minute value [{}] (possible values may be between 0 and 59 incl.)";
 minute);
 }
 return minute; 
 case VALUE_STRING:

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content