Updated roles roles file – How to solve related issues

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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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);




 

Run the Check-Up to get a customized report like this:

Analyze your cluster