Failed to auto-resolve http publish port; multiple bound addresses – Elasticsearch Error How To Solve Related Issues


Failed to auto-resolve http publish port; multiple bound addresses – Elasticsearch Error How To Solve Related Issues

Opster Team

July-20, 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 that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to auto-resolve http publish port; multiple bound addresses ” 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: Node.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”Failed to auto-resolve http publish port; multiple bound addresses”classname  is AbstractHttpServerTransport.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

publishPort = ports.iterator().next().value;
  }
  }
 
  if (publishPort 

 

Optimize Elasticsearch Performance

Try The Tool