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

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

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.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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) {


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?