Initializing . – 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 ” Initializing . ” 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 “initializing …” classname is Node.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         tmpSettings = TribeService.processSettings(tmpSettings);

        ESLogger logger = Loggers.getLogger(Node.class; tmpSettings.get("name"));
        logger.info("version[{}]; pid[{}]; build[{}/{}]"; version; JvmInfo.jvmInfo().pid(); Build.CURRENT.hashShort(); Build.CURRENT.timestamp());

        logger.info("initializing ...");

        if (logger.isDebugEnabled()) {
            logger.debug("using config [{}]; data [{}]; logs [{}]; plugins [{}]";
                    tmpEnv.configFile(); Arrays.toString(tmpEnv.dataFiles()); tmpEnv.logsFile(); tmpEnv.pluginsFile());
        }




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content