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

transport authenticationfailedt; principal=; action=; 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=; 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

                 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;
                            message.getClass().getSimpleName(); opaqueId());
                }
            }
        }




 

Run the Check-Up to get a customized report like this:

Analyze your cluster