Could not parse time . time format must be in the form of hh:mm – Elasticsearch Error How To Solve Related Issues



Could not parse time . time format must be in the form of hh:mm – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 

 

This guide will help you check for common problems that cause the log “could not parse time . time format must be in the form of hh:mm” 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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”could not parse time [{}]. time format must be in the form of hh:mm”classname  is DayTimes.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
  int[] hour;
  int[] minute;
  int i = time.indexOf(":");
  if (i = 0) {
  throw new ElasticsearchParseException("could not parse time [{}]. time format must be in the form of hh:mm"; time);
  }
  String hrStr = time.substring(0; i);

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Java format yyyy-MM-dd'T'HH:mm:ss.SSSz to yyyy-mm-dd HH:mm:ss -views 296,813 ,score 50

Deserialize Java 8 LocalDateTime with JacksonMapper -views   83,823,score 36



Find Configuration Errors

Analyze Now