# ElasticSearch, Kibana & Logstash Auto-Upgrading

**URL:** <https://discuss.elastic.co/t/elasticsearch-kibana-logstash-auto-upgrading/175565>\
**Category:** Elasticsearch\
**Created:** [April 5, 2019, 10:04am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-logstash-auto-upgrading/175565 "2019-04-05T10:04:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hazoopr](https://avatars.discourse-cdn.com/v4/letter/h/c6cbf5/32.png) [@Hazoopr](https://discuss.elastic.co/u/Hazoopr)\
**Post date:** [April 5, 2019, 10:04am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-logstash-auto-upgrading/175565/1 "2019-04-05T10:04:41Z")

</div>

`Apr 01 10:15:09 <hostname -f> kibana[24636]: {"type":"log","@timestamp":"2019-04-01T10:15:09Z","tags":["status","plugin:maps@6.7.0","info"],"pid":24636,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.7.0 on all nodes. I found the following incompatible nodes in your cluster: v6.6.2 @ <ipaddr_1>:9200 (<ipaddr_1>), v6.6.2 @ <ipaddr_3>:9200 (<ipaddr_3>), v6.6.2 @ <ipaddr_2>:9200 (<ipaddr_2>)"}`

1. ElasticSearch, Kibana & Logstash Auto-Upgrading.
2. There is usual behavior for this, As auto-upgrading is happening on month end.
3. Initially, we installed the version 6.5.0 & Current Version is 6.7.0 [Two Upgrades happened] in 3 months.
4. This issue gets identified on Kibana UI as it results in "Kibana server is not ready yet"

Please assist on the same as we have dependencies with other API connected with ELK stack causing uncertainty.

---

<div class="post-metadata">

**Author:** ![Hazoopr](https://avatars.discourse-cdn.com/v4/letter/h/c6cbf5/32.png) [@Hazoopr](https://discuss.elastic.co/u/Hazoopr)\
**Post date:** [April 9, 2019, 6:44am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-logstash-auto-upgrading/175565/2 "2019-04-09T06:44:56Z")

</div>

Any help here please.  
Again it got auto upgrade today.

`Apr 09 09:37:32 <hostname -f> kibana[2457]: {"type":"log","@timestamp":"2019-04-09T09:37:32Z","tags":["warning"],"pid":2457,"kibanaVersion":"6.7.1","nodes":[{"version":"6.7.0","http":{"publish_address":"<ip1>:9200"},"ip":"<ip1>"},{"version":"6.7.0","http":{"publish_address":"<ip3>:9200"},"ip":"<ip3>"},{"version":"6.7.0","http":{"publish_address":"<ip2>:9200"},"ip":"<ip2>"}],"message":"You're running Kibana 6.7.1 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatibility issues: v6.7.0 @ <ip1>:9200 (<ip1>), v6.7.0 @ <ip3>:9200 (<ip3>), v6.7.0 @ <ip2>:9200 (<ip2>)"}`

---

<div class="post-metadata">

**Author:** ![Hazoopr](https://avatars.discourse-cdn.com/v4/letter/h/c6cbf5/32.png) [@Hazoopr](https://discuss.elastic.co/u/Hazoopr)\
**Post date:** [April 10, 2019, 9:28am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-logstash-auto-upgrading/175565/3 "2019-04-10T09:28:50Z")

</div>

Issue resolved as it was due to yum-cron and appropriate config changes made it work.

_Well, Here experienced one of the most responsive communities in the world_

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 8, 2019, 9:28am UTC](https://discuss.elastic.co/t/elasticsearch-kibana-logstash-auto-upgrading/175565/4 "2019-05-08T09:28:52Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.