Invalid time minute value possible values may be between 0 and 59 – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when an invalid minute value is inputted in Elasticsearch. The minute value should be between 0 and 59, but a value outside this range has been entered. To resolve this issue, you should check the inputted time value and ensure that the minute value is within the acceptable range. If you’re using a script or application to input the time, ensure it’s correctly formatted to prevent such 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 ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “invalid time minute value [{}] (possible values may be between 0 and 59” class name is DayTimes.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 case VALUE_STRING:
 String value = parser.text();
 try {
 minute = Integer.valueOf(value);
 if (DayTimes.validMinute(minute) == false) {
 throw new ElasticsearchParseException("invalid time minute value [{}] (possible values may be between 0 and 59 " +
 "incl.)"; minute);
 }
 return minute;
 } catch (NumberFormatException nfe) {
 throw new ElasticsearchParseException("invalid time minute value [{}]"; value);

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?