# Trying out Watcher but once installed, Elasticsearch feed stops

**URL:** https://discuss.elastic.co/t/trying-out-watcher-but-once-installed-elasticsearch-feed-stops/25332
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [July 10, 2015, 4:10pm UTC](https://discuss.elastic.co/t/trying-out-watcher-but-once-installed-elasticsearch-feed-stops/25332 "2015-07-10T16:10:01Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![dmccuk](https://avatars.discourse-cdn.com/v4/letter/d/3d9bf3/32.png) [@dmccuk](https://discuss.elastic.co/u/dmccuk)
#### Post date: [July 14, 2015, 11:26am UTC](https://discuss.elastic.co/t/trying-out-watcher-but-once-installed-elasticsearch-feed-stops/25332/5 "2015-07-14T11:26:01Z")

</div>

Actually I think I fixed it. Checking that alert pushed me to find this post:

> [@After install watcher logstash cannot join the cluster](https://discuss.elastic.co/t/after-install-watcher-logstash-cannot-join-the-cluster/1744):
>
> Hello good people, I have 3 nodes cluster and 2 logstash instance use elasticsearch node output. After installing watcher for all 3 nodes, the logstash instances repeatedly showing the following warning and cannot do anything more. WARN: org.elasticsearch.transport.netty: [logstash-\*\*\*\*\*\*\*5-6181-2044] Message not fully read (request) for [4860] and action [discovery/zen/join/validate], resetting INFO: org.elasticsearch.discovery.zen: [logstash-\*\*\*\*\*\*\*5-6181-2044] failed to send join request t…

I updated my output protocol and it kicked back into life. Kibana3 still wasn't showing me the output so i change this line back to port 9200 and the data appeared.

```
elasticsearch: "http://"+window.location.hostname+":9200",

```

Hopefully i can get on with testing watcher now.

Regards

Dennis

---

_[View the full topic](https://discuss.elastic.co/t/trying-out-watcher-but-once-installed-elasticsearch-feed-stops/25332)._