Could not find default account defaultAccountName – How to solve this Elasticsearch exception

Opster Team

August-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 Elasticsearch is unable to locate the default account specified in the configuration. This could be due to a typo in the account name, the account not being created, or the account not being set as default. To resolve this issue, you can check the account name for typos, ensure the account is created, or set the account as default in the Elasticsearch configuration.

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 ” could not find default account [” + defaultAccountName + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “could not find default account [” + defaultAccountName + “]” class name is NotificationService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return accounts.values().iterator().next();
 }
 } else {
 final LazyInitializable account = accounts.get(defaultAccountName);
 if (account == null) {
 throw new SettingsException("could not find default account [" + defaultAccountName + "]");
 }
 return account;
 }
 }

 

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?