Users file changed updating users – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when the Elasticsearch users file is modified while the system is running. Elasticsearch automatically detects changes in the users file and updates the users accordingly. This is not necessarily an error, but more of an informational message. If you want to avoid seeing this message, you can stop Elasticsearch, make your changes to the users file, and then restart Elasticsearch. Alternatively, you can ignore this message if the changes to the users file were intentional and you want them to be applied immediately.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” users file [{}] changed. updating users… ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “users file [{}] changed. updating users…” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    private void tryReload() {
        final Map previousUsers = users;
        users = parseFileLenient(file; logger; settings);

        if (Maps.deepEquals(previousUsers; users) == false) {
  "users file [{}] changed. updating users..."; file.toAbsolutePath());


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?