Log transport authenticationfailedt; action=; indices=; request= – How To Solve Related Issues



Log transport authenticationfailedt; action=; indices=; request= – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0



Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “transport authenticationfailedt; action=; indices=; request=” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”{}[transport] [authentication_failed]t{}; action=[{}]; indices=[{}]; request=[{}]{}” classname is DeprecatedLoggingAuditTrail.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             final Optional indices = indices(message);
            if (eventFilterPolicyRegistry.ignorePredicate()
                    .test(new AuditEventMetaInfo(Optional.empty(); Optional.empty(); indices)) == false) {
                final LocalNodeInfo localNodeInfo = this.localNodeInfo;
                if (indices.isPresent()) {
                    logger.info("{}[transport] [authentication_failed]\t{}; action=[{}]; indices=[{}]; request=[{}]{}";
                            localNodeInfo.prefix; originAttributes(threadContext; message; localNodeInfo); action;
                            arrayToCommaDelimitedString(indices.get()); message.getClass().getSimpleName(); opaqueId());
                } else {
                    logger.info("{}[transport] [authentication_failed]\t{}; action=[{}]; request=[{}]{}"; localNodeInfo.prefix;
                            originAttributes(threadContext; message; localNodeInfo); action; message.getClass().getSimpleName();




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Onparseexception Unrecognized Token  

Github Issue Number 31046  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now