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

String currentFieldName = null;
 while ((token = parser.nextToken()) != XContentParser.Token.END_OBJECT) {
 if (token == XContentParser.Token.FIELD_NAME) {
 currentFieldName = parser.currentName();
 } else if (currentFieldName == null) {
 throw new ElasticsearchParseException("could not parse email template. empty [{}] field"; fieldName);
 } else if (Email.Field.BODY_TEXT.match(currentFieldName; parser.getDeprecationHandler())) {
 builder.textBody(TextTemplate.parse(parser));
 } else if (Email.Field.BODY_HTML.match(currentFieldName; parser.getDeprecationHandler())) {
 builder.htmlBody(TextTemplate.parse(parser));
 } else {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content