Could not update watcher stopped status to ; source – How to solve related issues

Average Read Time

2 Mins

Could not update watcher stopped status to ; source – 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 ” Could not update watcher stopped status to ; source ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin and source.

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 “Could not update watcher stopped status to [{}]; source [{}]” classname is TransportWatcherServiceAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         }
                    }

                    
Override
                    public void onFailure(String source; Exception e) {
                        logger.error(new ParameterizedMessage("could not update watcher stopped status to [{}]; source [{}]";
                                manuallyStopped; source); e);
                        listener.onFailure(e);
                    }
                });
    }



 

Try AutoOps to detect and fix issues in your cluster:

Watch Product Tour

Get Started Free

Skip to content