Could not read the current timestamp – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to fetch the current timestamp from the system. This could be due to a system clock issue, a problem with the Elasticsearch node, or a misconfiguration in the Elasticsearch settings. To resolve this issue, you can try synchronizing your system clock, restarting the Elasticsearch node, or checking your Elasticsearch configuration for any errors related to date and time settings.

This guide will help you check for common problems that cause the log ” could not read the current timestamp ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “could not read the current timestamp” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (text.startsWith("now")) {
 try {
 // TODO only millisecond granularity here!
 time = Instant.ofEpochMilli(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) {