transport authenticationfailedt; principal=; action=; indices=; request= – How to solve related issues

Average Read Time

2 Mins

transport authenticationfailedt; principal=; 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 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 ” transport authenticationfailedt; principal=; action=; indices=; request= ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: 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 “{}[transport] [authentication_failed]t{}; principal=[{}]; 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.of(token); Optional.empty(); indices)) == false) {
                final LocalNodeInfo localNodeInfo = this.localNodeInfo;
                if (indices.isPresent()) {
                    logger.info("{}[transport] [authentication_failed]\t{}; principal=[{}]; action=[{}]; indices=[{}]; request=[{}]{}";
                            localNodeInfo.prefix; originAttributes(threadContext; message; localNodeInfo); token.principal(); action;
                            arrayToCommaDelimitedString(indices.get()); message.getClass().getSimpleName(); opaqueId());
                } else {
                    logger.info("{}[transport] [authentication_failed]\t{}; principal=[{}]; action=[{}]; request=[{}]{}";
                            localNodeInfo.prefix; originAttributes(threadContext; message; localNodeInfo); token.principal(); action;




 

Try AutoOps to detect and fix issues in your cluster:

Watch Product Tour

Get Started Free

Skip to content