# X-pack 6.2.3 issue after upgrade
**URL:** https://discuss.elastic.co/t/x-pack-6-2-3-issue-after-upgrade/125225
**Category:** Elasticsearch
**Created:** [March 22, 2018, 3:53pm UTC](https://discuss.elastic.co/t/x-pack-6-2-3-issue-after-upgrade/125225 "2018-03-22T15:53:48Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@MrThecrackerx](https://discuss.elastic.co/u/MrThecrackerx)
#### Post date: [March 22, 2018, 3:53pm UTC](https://discuss.elastic.co/t/x-pack-6-2-3-issue-after-upgrade/125225/1 "2018-03-22T15:53:48Z")
Hi All
i upgraded from elasticsearch 5.6.8 to 6.2.3 and delete all the system indices and removed x-pack and installed it again from scratch. i keep getting this error due to mapping. Please help how to resolve this
[2018-03-22T11:52:57,816][ERROR][o.e.x.m.e.l.LocalExporter] failed to set monitoring watch [uCH4SDOQS8aynnLkTqPnvg\_elasticsearch\_nodes]
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:501) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.index.mapper.MapperService.internalMerge(MapperService.java:353) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:277) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$IndexCreationTask.execute(MetaDataCreateIndexService.java:444) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:45) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:643) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:273) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:198) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:133) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:573) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:244) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:207) [elasticsearch-6.2.3.jar:6.2.3]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0\_161]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0\_161]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_161]
[2018-03-22T11:52:57,819][ERROR][o.e.x.m.e.l.LocalExporter] failed to set monitoring watch [uCH4SDOQS8aynnLkTqPnvg\_kibana\_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:501) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.index.mapper.MapperService.internalMerge(MapperService.java:353) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:277) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$IndexCreationTask.execute(MetaDataCreateIndexService.java:444) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:45) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:643) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:273) ~[elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:198) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:133) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:573) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:244) [elasticsearch-6.2.3.jar:6.2.3]
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:207) [elasticsearch-6.2.3.jar:6.2.3]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0\_161]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0\_161]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_161]
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [March 22, 2018, 3:58pm UTC](https://discuss.elastic.co/t/x-pack-6-2-3-issue-after-upgrade/125225/2 "2018-03-22T15:58:48Z")
Hey,
my assumption is, that you still have old index templates on your cluster. Can you delete the `triggered_watches` and the `watches` templates, **after** that delete the watches and triggered\_watches indices and then retry.
--Alex
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [March 22, 2018, 3:59pm UTC](https://discuss.elastic.co/t/x-pack-6-2-3-issue-after-upgrade/125225/3 "2018-03-22T15:59:36Z")
Also, when upgrading from 5.6 we have a dedicated helping API for that. See [https://www.elastic.co/guide/en/elastic-stack/6.2/upgrading-elastic-stack.html#upgrade-internal-indices](https://www.elastic.co/guide/en/elastic-stack/6.2/upgrading-elastic-stack.html#upgrade-internal-indices)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 19, 2018, 4:00pm UTC](https://discuss.elastic.co/t/x-pack-6-2-3-issue-after-upgrade/125225/4 "2018-04-19T16:00:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.