Malformed – 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 ” malformed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search and aggregations.

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 “malformed [“classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (Double.isNaN(lon)) {
 lon = parser.doubleValue();
 } else if (Double.isNaN(lat)) {
 lat = parser.doubleValue();
 } else {
 throw new ParsingException(parser.getTokenLocation(); "malformed [" + ORIGIN_FIELD.getPreferredName()
 + "]: a geo point array must be of the form [lon; lat]");
 return new GeoPoint(lat; lon);


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content