Failed to get users that already exist skipping user import – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

Briefly, this error occurs when Elasticsearch is unable to retrieve existing users during a user import process, possibly due to incorrect user credentials, network issues, or insufficient permissions. To resolve this, you can verify the user credentials, check the network connectivity, ensure the Elasticsearch cluster is running, and confirm that the user has the necessary permissions to perform the import operation. Additionally, check the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” failed to get users that already exist; skipping user import ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “failed to get users that already exist; skipping user import” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 Map userToRoles = FileUserRolesStore.parseFile(usersRolesFile; logger);
 Set existingUsers;
 try {
 existingUsers = getUsersThatExist(terminal; env.settings(); env; options);
 } catch (Exception e) {
 throw new ElasticsearchException("failed to get users that already exist; skipping user import"; e);
 if (usersToMigrate.length == 0) {
 usersToMigrate = userToHashedPW.keySet().toArray(new String[userToHashedPW.size()]);
 for (String user : usersToMigrate) {