# ES 5.4 =\> 6.0 Upgrade. Watcher Issues
**URL:** https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481
**Category:** Elasticsearch
**Created:** [November 21, 2017, 1:07am UTC](https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481 "2017-11-21T01:07:05Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@aballman](https://discuss.elastic.co/u/aballman)
#### Post date: [November 21, 2017, 1:07am UTC](https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481/1 "2017-11-21T01:07:06Z")
I have upgrade ES from 5.4 to 6.0, including Kibana and all the plugins we have installed. They are discovery-ec2, repository-s3, and x-pack. I followed the upgrade instructions as listed here: [https://www.elastic.co/guide/en/elasticsearch/reference/6.0/restart-upgrade.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.0/restart-upgrade.html). Everything went well including remapping the Kibana index. The logs for my cluster keep dumping the following though...
`[WARN][o.e.x.w.WatcherLifeCycleService] [MEEC-x7] not starting watcher, upgrade API run required: .watches[true], .triggered_watches[false]`
I couldn't find any documentation to help resolve my situation. I checked breaking changes in 6.0 [https://www.elastic.co/guide/en/kibana/current/breaking-6.0.0-xkb.html](https://www.elastic.co/guide/en/kibana/current/breaking-6.0.0-xkb.html) and it doesn't mention anything about an upgrade API run.
I searched for the log string and variations thereof, I could only find references to ES 2.4. What am I missing? What do I have to nuke and/or massage to get this to stop complaining?
---
### Author:  [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)
#### Post date: [November 24, 2017, 11:47am UTC](https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481/2 "2017-11-24T11:47:37Z")
Hello,
You should have gone through 5.6 before upgrading to 6.0, at least for Kibana.
There is an upgrade assistant in 5.6 that will run the upgrade API for you on all indices and also mention the breaking changes between the versions.
You can still run it now, by connecting a 5.6 Kibana to your current 6.0 cluster and running the upgrade assistant for there, just to fix your watcher problem.
You can find the guide here and assistant is in the Management page of Kibana:
[https://www.elastic.co/guide/en/kibana/6.0/xpack-upgrade-assistant.html](https://www.elastic.co/guide/en/kibana/6.0/xpack-upgrade-assistant.html)
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [November 24, 2017, 6:57pm UTC](https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481/3 "2017-11-24T18:57:28Z")
you can also just call the endpoints manually, see
[https://www.elastic.co/guide/en/elasticsearch/reference/6.0/migration-api-assistance.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.0/migration-api-assistance.html)
[https://www.elastic.co/guide/en/elasticsearch/reference/6.0/migration-api-upgrade.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.0/migration-api-upgrade.html)
---
### Author:  [@aballman](https://discuss.elastic.co/u/aballman)
#### Post date: [November 27, 2017, 9:21pm UTC](https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481/4 "2017-11-27T21:21:39Z")
Thank you, this resolved my issues.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 25, 2017, 9:22pm UTC](https://discuss.elastic.co/t/es-5-4-6-0-upgrade-watcher-issues/108481/5 "2017-12-25T21:22:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.