Failed to start index audit trail services – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch is unable to start the index audit trail services, which are crucial for logging and tracking changes in the index. This could be due to insufficient permissions, misconfiguration, or resource constraints. To resolve this issue, you can check and adjust the permissions, verify the configuration settings, or increase the system resources. Additionally, ensure that the Elasticsearch service is running properly and that there are no network connectivity issues.

This guide will help you check for common problems that cause the log ” failed to start index audit trail services ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index.

Log Context

Log “failed to start index audit trail services” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            if (state() == IndexAuditTrail.State.INITIALIZED && canStart(event)) {
                threadPool.generic().execute(new AbstractRunnable() {

                    public void onFailure(Exception throwable) {
                        logger.error("failed to start index audit trail services"; throwable);
                        assert false : "security lifecycle services startup failed";

                    public void doRun() {


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?