# Broke Watcher on ES6
**URL:** https://discuss.elastic.co/t/broke-watcher-on-es6/109665
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [November 29, 2017, 11:55pm UTC](https://discuss.elastic.co/t/broke-watcher-on-es6/109665 "2017-11-29T23:55:00Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@djtecha](https://discuss.elastic.co/u/djtecha)
#### Post date: [November 29, 2017, 11:55pm UTC](https://discuss.elastic.co/t/broke-watcher-on-es6/109665/1 "2017-11-29T23:55:00Z")
So, I ran into some oddities after upgrading from 5.6 and had zero watches so figured I'd just delete the index and let ES recreate it. Upon rebooting my full cluster the index doesn't appear to be recreated and I'm just stuck with this log repeating over and over. WOndering if it's come up before.
> [2017-11-29T23:50:48,973][ERROR][o.e.x.m.e.l.LocalExporter] failed to set monitoring watch [MASmnQTrSXuU4\_Ls7KXg7w\_logstash\_version\_mismatch]
> java.lang.IllegalArgumentException: Rejecting mapping update to [.watches] as the final mapping would have more than 1 type: [watch, doc]
> at org.elasticsearch.index.mapper.MapperService.internalMerge(MapperService.java:494) ~[elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.index.mapper.MapperService.internalMerge(MapperService.java:350) ~[elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:274) ~[elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$1.execute(MetaDataCreateIndexService.java:410) ~[elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:45) ~[elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:640) ~[elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:270) ~[elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:195) [elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:130) [elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150) [elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188) [elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569) [elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:247) [elasticsearch-6.0.0.jar:6.0.0]
> at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:210) [elasticsearch-6.0.0.jar:6.0.0]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0\_141]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0\_141]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_141]
---
### Author:  [@djtecha](https://discuss.elastic.co/u/djtecha)
#### Post date: [November 30, 2017, 12:31am UTC](https://discuss.elastic.co/t/broke-watcher-on-es6/109665/2 "2017-11-30T00:31:35Z")
Ok got it, had some stale templates breaking things. After I cleared those out this worked just fine.
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [November 30, 2017, 8:24am UTC](https://discuss.elastic.co/t/broke-watcher-on-es6/109665/3 "2017-11-30T08:24:11Z")
Out of curiosity: Have you run the upgrade assistant before and upgraded the watches and triggered watches index?
---
### Author:  [@djtecha](https://discuss.elastic.co/u/djtecha)
#### Post date: [November 30, 2017, 5:41pm UTC](https://discuss.elastic.co/t/broke-watcher-on-es6/109665/4 "2017-11-30T17:41:00Z")
The watches and triggered indexes refused to upgrade with the upgrade API and it was unused at the time so I didn't care to fix it then. Lesson learned. 🙂
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [November 30, 2017, 11:01pm UTC](https://discuss.elastic.co/t/broke-watcher-on-es6/109665/5 "2017-11-30T23:01:24Z")
Do you have any errors or logs, why the upgrade was refused? I am getting curious now... anything would help 🙂
--Alex
---
### Author:  [@djtecha](https://discuss.elastic.co/u/djtecha)
#### Post date: [November 30, 2017, 11:23pm UTC](https://discuss.elastic.co/t/broke-watcher-on-es6/109665/6 "2017-11-30T23:23:02Z")
Sadly no, usually I like to help, but was in a time crunch. But it was a
pretty basic setup with no watches even started. SO maybe it could be
repo'd going from 5.6 to 6.0
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 28, 2017, 11:23pm UTC](https://discuss.elastic.co/t/broke-watcher-on-es6/109665/7 "2017-12-28T23:23:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.