Failed to add plugin – 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 analyzes 2 JSON files to detect many errors.

Briefly, this error message indicates that Elasticsearch was unable to add a plugin. The reason for this error could be a problem with the Elasticsearch instance or a problem with the plugin being added. To resolve the issue, the plugin should be checked for issues or Elasticsearch should be restarted.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Failed to add plugin ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin and plugins.

Log Context

Log “failed to add plugin [” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    addURL.invoke(classLoader; libFile.toURI().toURL());
            } catch (Throwable e) {
                logger.warn("failed to add plugin [" + plugin + "]"; e);

    private ImmutableList> loadPluginsFromClasspath(Settings settings) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content