Loaded . sites – How to solve related issues

Average Read Time

2 Mins

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 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 ” 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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()) {


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

Analyze your cluster