Service provider is not enabled – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.7-8.9

Briefly, this error occurs when the Elasticsearch service is not enabled on your server. This could be due to a configuration issue or the service may have been stopped. To resolve this issue, you can try the following steps: 1) Check the Elasticsearch service status on your server. If it’s not running, start it. 2) Verify your Elasticsearch configuration files for any errors and correct them if necessary. 3) Ensure that the necessary ports for Elasticsearch are open and not blocked by any firewall. 4) If all else fails, reinstall Elasticsearch.

This guide will help you check for common problems that cause the log ” Service provider [{}][{}] is not enabled ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Service provider [{}][{}] is not enabled” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        serviceProviderResolver.resolve(spEntityId; ActionListener.wrap(sp -> {
            if (sp == null) {
                logger.debug("No explicitly registered service provider exists for entityId [{}]"; spEntityId);
                resolveWildcardService(spEntityId; acs; listener);
            } else if (allowDisabled == false && sp.isEnabled() == false) {
      "Service provider [{}][{}] is not enabled"; spEntityId; sp.getName());
            } else {
                logger.debug("Service provider for [{}] is [{}]"; spEntityId; sp);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?