No network address found. ignoring . – How to solve related issues

Average Read Time

2 Mins

No network address found. ignoring . – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” No network address found. ignoring . ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery, discovery-azure-classic, hosts, network and plugins.

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 “No network address found. ignoring [{}]…” classname is AzureUnicastHostsProvider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
            for (RoleInstance instance : deployment.getRoleInstances()) {
                final String networkAddress = resolveInstanceAddress(hostType; instance);
                if (networkAddress == null) {
                    // We have a bad parameter here or not enough information from azure
                    logger.warn("no network address found. ignoring [{}]..."; instance.getInstanceName());
                    continue;
                }

                try {
                    // we only limit to 1 port per address; makes no sense to ping 100 ports




 

Run the Check-Up to get customized insights on your system:

Analyze your cluster