-non-loopback- is deprecated as it picks an arbitrary interface. specify explicit scope(s); interface(s); address(es); or hostname(s) instead – How to solve related issues

Opster Team

Feb-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 ” -non-loopback- is deprecated as it picks an arbitrary interface. specify explicit scope(s); interface(s); address(es); or hostname(s) instead ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: network.

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 “_non_loopback_ is deprecated as it picks an arbitrary interface. specify explicit scope(s); interface(s); address(es); or hostname(s) instead” classname is NetworkService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     return NetworkUtils.getFirstNonLoopbackAddresses();
                case "non_loopback:ipv4":
                    logger.warn("_non_loopback_ is deprecated as it picks an arbitrary interface. specify explicit scope(s); interface(s); address(es); or hostname(s) instead");
                    return NetworkUtils.filterIPV4(NetworkUtils.getFirstNonLoopbackAddresses());
                case "non_loopback:ipv6":
                    logger.warn("_non_loopback_ is deprecated as it picks an arbitrary interface. specify explicit scope(s); interface(s); address(es); or hostname(s) instead");
                    return NetworkUtils.filterIPV6(NetworkUtils.getFirstNonLoopbackAddresses());
                default:
                    /* an interface specification */
                    if (host.endsWith(":ipv4")) {
                        host = host.substring(0; host.length() - 5);




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content