Could not parse as address. address must either be a string (RFC822 encoded) or – 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 as address. address must either be a string (RFC822 encoded) or ” 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 [{}] as address. address must either be a string (RFC822 encoded) or”classname  is Email.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} catch (AddressException ae) {
 throw new ElasticsearchParseException("could not parse [" + field + "] as address"; ae);
 } 
 }
 throw new ElasticsearchParseException("could not parse [{}] as address. address must either be a string (RFC822 encoded) or " +
 "an object specifying the address [name] and [email]"; field);
 } 
 public static Address parse(Settings settings; String name) {
 String value = settings.get(name);

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content