is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed. – How to solve related issues

is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed. – 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 ” is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed. ” 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: bootstrap.

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 “{} is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed.” classname is Bootstrap.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     }

    private static void checkUnsetAndMaybeExit(String confFileSetting; String settingName) {
        if (confFileSetting != null && confFileSetting.isEmpty() == false) {
            ESLogger logger = Loggers.getLogger(Bootstrap.class);
            logger.info("{} is no longer supported. elasticsearch.yml must be placed in the config directory and cannot be renamed."; settingName);
            exit(1);
        }
    }

    
SuppressForbidden(reason = "Allowed to exit explicitly in bootstrap phase")



 

Run the Check-Up to get a customized report like this:

Analyze your cluster