File settings service up and running tid= – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.4-8.9

Briefly, this error occurs when Elasticsearch is successfully started and the file settings service is running. This is not an error message but an informational log message indicating that the service is up and running. If you’re seeing this message frequently and it’s causing concern, you may want to adjust your logging levels to reduce the verbosity. Alternatively, if you’re experiencing issues with Elasticsearch despite this message, the problem lies elsewhere and you should look for other error messages or investigate your cluster health and configuration.

This guide will help you check for common problems that cause the log ” file settings service up and running [tid={}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: settings.

Log Context

Log “file settings service up and running [tid={}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    protected final void watcherThread() {
        try {
  "file settings service up and running [tid={}]"; Thread.currentThread().getId());

            Path path = watchedFile();

            if (Files.exists(path)) {
                logger.debug("found initial operator settings file [{}]; applying..."; path);


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?