Failed to get token since index is not available – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.1

Briefly, this error occurs when Elasticsearch tries to retrieve a token from an index that is not available or does not exist. This could be due to the index being deleted, not yet created, or a network issue preventing access. To resolve this issue, you can: 1) Check if the index exists and recreate it if necessary, 2) Ensure the Elasticsearch cluster is running and accessible, 3) Check your network connectivity, and 4) Review your application’s code to ensure it’s not trying to access an index before it’s created.

This guide will help you check for common problems that cause the log ” failed to get token [{}] since index is not available ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index.

Log Context

Log “failed to get token [{}] since index is not available” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    try {
                        final byte[] iv = in.readByteArray();
                        final Cipher cipher = getDecryptionCipher(iv; decodeKey; version; decodedSalt);
                        decryptTokenId(in; cipher; version; ActionListener.wrap(tokenId -> {
                            if (securityIndex.isAvailable() == false) {
                                logger.warn("failed to get token [{}] since index is not available"; tokenId);
                            } else {
                                    ex -> listener.onFailure(traceLog("prepare security index"; tokenId; ex));
                                    () -> {