Modules ; plugins ; 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 ” Modules ; plugins ; sites ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins.

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 “modules {}; plugins {}; sites {}” classname is PluginsService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         }
        for (PluginInfo pluginInfo : info.getPluginInfos()) {
            jvmPluginNames.add(pluginInfo.getName());
        }

        logger.info("modules {}; plugins {}; sites {}"; moduleNames; jvmPluginNames; sitePlugins);

        Map> onModuleReferences = new HashMap();
        for (Plugin plugin : jvmPlugins.values()) {
            List list = new ArrayList();
            for (Method method : plugin.getClass().getMethods()) {




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content