Could not update watcher stopped status to source – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch fails to update the status of a watcher to ‘stopped’. This could be due to insufficient permissions, a network issue, or a problem with the watcher itself. To resolve this, you can try the following: 1) Check and adjust the user permissions if necessary, 2) Verify the network connectivity between the nodes, 3) Inspect the watcher for any configuration issues, and 4) Restart the Elasticsearch service. If the problem persists, consider checking the Elasticsearch logs for more detailed error information.

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, source.

Log Context

Log “could not update watcher stopped status to [{}]; source [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


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


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?