Could not parse ” + field + ” as address – Elasticsearch Error How To Solve Related Issues



Could not parse ” + field + ” as address – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

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

 

This guide will help you check for common problems that cause the log “could not parse ” + field + ” as address” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”could not parse [” + field + “] as address”classname  is Email.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new ElasticsearchParseException(msg);
  }
  try {
  return name != null ? new Email.Address(email; name) : new Email.Address(email);
  } 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);

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Logstash does not parse json -views 27,188 ,score 10

elasticsearch watcher could not parse search input -views   1,296,score 1



Find Configuration Errors

Analyze Now