Failed to find token for refresh token after attempts – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error 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 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 and refresh.

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 find token for refresh token [{}] after [{}] attempts” classname is TokenService.java.
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)
                .setQuery(QueryBuilders.boolQuery()
                    .filter(QueryBuilders.termQuery("doc_type"; "token"))




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content