Failed to auto-resolve publish port” + profileExplanation + “; multiple bound addresses – 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 ” Failed to auto-resolve publish port” + profileExplanation + “; multiple bound addresses ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node.

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 “Failed to auto-resolve publish port” + profileExplanation + “; multiple bound addresses”classname  is TcpTransport.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 } 
 if (publishPort < 0) {
 String profileExplanation = profileSettings.isDefaultProfile ? "" : " for profile " + profileSettings.profileName;
 throw new BindTransportException("Failed to auto-resolve publish port" + profileExplanation + "; multiple bound addresses " +
 boundAddresses + " with distinct ports and none of them matched the publish address (" + publishInetAddress + "). " +
 "Please specify a unique port by setting " + TransportSettings.PORT.getKey() + " or " +
 TransportSettings.PUBLISH_PORT.getKey());
 }
 return publishPort;

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content