Failed to send exception response for action – 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 ” Failed to send exception response for action ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin and response.

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 “Failed to send exception response for action [” classname is SecurityServerTransportInterceptor.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 public void onFailure(Exception e) {
                    try {
                        channel.sendResponse(e);
                    } catch (Exception e1) {
                        e1.addSuppressed(e);
                        logger.warn("failed to send exception response for action [" + action + "]"; e1);
                    }
                }

                
Override
                protected void doRun() throws Exception {



 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content