Log Loaded . sites – How To Solve Related Issues



Log Loaded . sites – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0



Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Loaded . sites” 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: plugins.


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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”loaded {}; sites {}” classname is PluginsService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             if (!missingPlugins.isEmpty()) {
                throw new ElasticsearchException("Missing mandatory plugins [" + Strings.collectionToDelimitedString(missingPlugins; "; ") + "]");
            }
        }

        logger.info("loaded {}; sites {}"; jvmPlugins.keySet(); sitePlugins);

        MapBuilder> onModuleReferences = MapBuilder.newMapBuilder();
        for (Plugin plugin : jvmPlugins.values()) {
            List list = Lists.newArrayList();
            for (Method method : plugin.getClass().getDeclaredMethods()) {




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Elasticsearch not starting -views 0.71 K ,score 1

Client Is Connecting Several Times  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now