Could not read the current timestamp – Elasticsearch Error How To Solve Related Issues



Could not read the current timestamp – 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 read the current timestamp” 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: .


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 read the current timestamp”classname  is JodaDateMathParser.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

String mathString;
  if (text.startsWith("now")) {
  try {
  time = now.getAsLong();
  } catch (Exception e) {
  throw new ElasticsearchParseException("could not read the current timestamp"; e);
  }
  mathString = text.substring("now".length());
  } else {
  int index = text.indexOf("||");
  if (index == -1) {

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 Logstash date parsing as timestamp using the date filter -views 76,147 ,score 25

How to make elasticsearch add the timestamp field to every document in all indices? -views   61,408,score 39



Find Configuration Errors

Analyze Now