Briefly, this error occurs when Elasticsearch is unable to locate the refresh token after multiple attempts. This could be due to an expired token, incorrect token, or issues with the token storage. To resolve this, you can try regenerating a new refresh token, ensuring the correct token is being used, or checking the token storage for any potential issues. If the problem persists, it may be necessary to debug the token generation and storage process to identify any underlying issues.
This guide will help you check for common problems that cause the log ” failed to find token from refresh token after all retries ” 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 from refresh token after all retries” classname is TokenService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
() -> findTokenFromRefreshToken(refreshToken; tokensIndexManager; backoff; listener);
backofTimeValue;
GENERIC
);
} else {
logger.warn("failed to find token from refresh token after all retries");
onFailure.accept(ex);
}
};
final SecurityIndexManager frozenTokensIndex = tokensIndexManager.freeze();
if (frozenTokensIndex.indexExists() == false) {
