Could not find token document with refreshtoken – 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 ” Could not find token document with refreshtoken ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: document and plugin.

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 “Could not find token document with refresh_token [{}]” classname is TokenService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         ActionListener.wrap(searchResponse -> {
                            if (searchResponse.isTimedOut()) {
                                attemptCount.incrementAndGet();
                                findTokenFromRefreshToken(refreshToken; listener; attemptCount);
                            } else if (searchResponse.getHits().getHits().length  1) {
                                onFailure.accept(new IllegalStateException("multiple tokens share the same refresh token"));
                            } else {
                                listener.onResponse(new Tuple(searchResponse; attemptCount));




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content