Could not parse response body it does not appear to be – 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 response body it does not appear to be ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: response and 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 response body [{}] it does not appear to be [{}]”classname  is ExecutableHttpInput.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else {
 payloadMap.putAll(parser.mapOrdered());
 }
 }
 } catch (Exception e) {
 throw new ElasticsearchParseException("could not parse response body [{}] it does not appear to be [{}]"; type(); ctx.id();
 response.body().utf8ToString(); contentType.shortName());
 }
 } else {
 payloadMap.put("_value"; response.body().utf8ToString());
 }

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content