Started – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch service has successfully started. It’s not an error message, but rather an informational message indicating that the Elasticsearch server is up and running. If you’re seeing this message, it means your Elasticsearch instance is operational. If you’re facing issues despite this message, the problem might lie elsewhere in your application or infrastructure. To resolve any issues, ensure your application is correctly configured to connect to the Elasticsearch server, check your network settings, and verify that your Elasticsearch queries are correctly formatted.

This guide will help you check for common problems that cause the log ” started {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node.

Log Context

Log “started {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            if (RemoteClusterPortSettings.REMOTE_CLUSTER_SERVER_ENABLED.get(environment.settings())) {
                writePortsFile("remote_cluster"; transport.boundRemoteAccessAddress());
        }"started {}"; transportService.getLocalNode());


        return this;


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?