# One cluster, Two Kibana servers for HA - Monitoring shows One

**URL:** <https://discuss.elastic.co/t/one-cluster-two-kibana-servers-for-ha-monitoring-shows-one/84322>\
**Category:** Kibana\
**Created:** [May 2, 2017, 8:08pm UTC](https://discuss.elastic.co/t/one-cluster-two-kibana-servers-for-ha-monitoring-shows-one/84322 "2017-05-02T20:08:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ben-10](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben-10/32/12306_2.png) [@ben-10](https://discuss.elastic.co/u/ben-10)\
**Post date:** [May 2, 2017, 8:08pm UTC](https://discuss.elastic.co/t/one-cluster-two-kibana-servers-for-ha-monitoring-shows-one/84322/1 "2017-05-02T20:08:43Z")

</div>

I have one elasticsearch cluster with 10 nodes. Two of those nodes are client nodes with Kibana installed for HA. Under the Monitoring Tab, cluster, Kibana instances, it will show one of the two nodes for a while and then it will switch to the other.

It never shows both of the nodes at the same time. Is this normal or broken?

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [May 3, 2017, 6:12pm UTC](https://discuss.elastic.co/t/one-cluster-two-kibana-servers-for-ha-monitoring-shows-one/84322/2 "2017-05-03T18:12:16Z")

</div>

This is most likely due to both instances having the same UUID. This could be caused by setting the original Kibana instance up and copying the directory to another machine. To resolve this, you can delete the `data/uuid` file from either (or both) of the Kibana instances.

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [May 3, 2017, 6:14pm UTC](https://discuss.elastic.co/t/one-cluster-two-kibana-servers-for-ha-monitoring-shows-one/84322/3 "2017-05-03T18:14:51Z")

</div>

Removing the `data/uuid` file from both instances would get you off to a clean start.

---

<div class="post-metadata">

**Author:** ![ben-10](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben-10/32/12306_2.png) [@ben-10](https://discuss.elastic.co/u/ben-10)\
**Post date:** [May 4, 2017, 2:32pm UTC](https://discuss.elastic.co/t/one-cluster-two-kibana-servers-for-ha-monitoring-shows-one/84322/4 "2017-05-04T14:32:42Z")

</div>

Spot on! After stopping the service, deleting `/var/lib/kibana/uuid` and restarting, the two Kibana instances have different UUID and they now both show up correctly! Thank you!

---

<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:** [June 1, 2017, 2:45pm UTC](https://discuss.elastic.co/t/one-cluster-two-kibana-servers-for-ha-monitoring-shows-one/84322/5 "2017-06-01T14:45:39Z")

</div>

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