Could not parse time value. expected either a string or a null value but found – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” could not parse time value. expected either a string or a null value but found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “could not parse time value. expected either a string or a null value but found [{}]”classname  is WatcherDateTimeUtils.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} catch (ElasticsearchParseException epe) {
 throw new ElasticsearchParseException("failed to parse time unit"; epe);
 } 
 }
 throw new ElasticsearchParseException("could not parse time value. expected either a string or a null value but found [{}] " +
 "instead"; token);
 } 
 /**
 * Parse a {@link TimeValue} with support for fractional values.

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content