Failed to find token for refresh token after attempts – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.1

Briefly, this error occurs when Elasticsearch cannot locate the token associated with a refresh token after multiple attempts. This could be due to the token being expired, deleted, or not correctly stored. To resolve this issue, you can try the following: 1) Ensure the token is not expired. If it is, generate a new one. 2) Check if the token was accidentally deleted. If so, create a new one. 3) Verify that the token is correctly stored and accessible by Elasticsearch. If not, adjust the storage settings or permissions.

This guide will help you check for common problems that cause the log ” Failed to find token for refresh token [{}] after [{}] attempts ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, refresh.

Log Context

Log “Failed to find token for refresh token [{}] after [{}] attempts” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    private void findTokenFromRefreshToken(String refreshToken; ActionListener> listener;
                                           AtomicInteger attemptCount) {
        if (attemptCount.get() > MAX_RETRY_ATTEMPTS) {
            logger.warn("Failed to find token for refresh token [{}] after [{}] attempts"; refreshToken; attemptCount.get());
            listener.onFailure(invalidGrantException("could not refresh the requested token"));
        } else {
            SearchRequest request = client.prepareSearch(SecurityIndexManager.SECURITY_INDEX_NAME)
                    .filter(QueryBuilders.termQuery("doc_type"; TOKEN_DOC_TYPE))


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?