Updated roles roles file – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Updated roles roles file ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-file and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Updated roles (roles file [{}] {})” classname is FileRolesStore.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         public synchronized void onFileChanged(Path file) {
            if (file.equals(FileRolesStore.this.file)) {
                final Map previousPermissions = permissions;
                try {
                    permissions = parseFile(file; logger; settings; licenseState);
                    logger.info("updated roles (roles file [{}] {})"; file.toAbsolutePath();
                        Files.exists(file) ? "changed" : "removed");
                } catch (Exception e) {
                    logger.error(
                            (Supplier>) () -> new ParameterizedMessage(
                                    "could not reload roles file [{}]. Current roles remain unmodified"; file.toAbsolutePath()); e);




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content