Failed to index audit message from queue – How To Solve Related Issues

Failed to index audit message from queue – 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 that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to index audit message from queue ” 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: index, plugin and queue.

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 “Failed to index audit message from queue” classname is IndexAuditTrail.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     logger.debug("index audit queue consumer interrupted"; e);
                    close();
                    break;
                } catch (Exception e) {
                    // log the exception and keep going
                    logger.warn("failed to index audit message from queue"; e);
                }
            }
            eventQueue.clear();
        }





 

Optimize Elasticsearch Performance

Try The Tool