Failed to parse indices privileges for role . cannot be an empty – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

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

This guide will help you check for common problems that cause the log ” failed to parse indices privileges for role . cannot be an empty ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices 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 “failed to parse indices privileges for role [{}]. [{}] cannot be an empty”classname  is RoleDescriptor.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (token == XContentParser.Token.VALUE_STRING) {
 names = new String[]{parser.text()};
 } else if (token == XContentParser.Token.START_ARRAY) {
 names = readStringArray(roleName; parser; false);
 if (names.length == 0) {
 throw new ElasticsearchParseException("failed to parse indices privileges for role [{}]. [{}] cannot be an empty " +
 "array"; roleName; currentFieldName);
 }
 } else {
 throw new ElasticsearchParseException("failed to parse indices privileges for role [{}]. expected field [{}] " +
 "value to be a string or an array of strings; but found [{}] instead"; roleName; currentFieldName; token);

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content