# Kibana 7.6 : Reported number of Kibana instance is false **URL:** \ **Category:** Kibana\ **Created:** [February 19, 2020, 11:10am UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946 "2020-02-19T11:10:56Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Travis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/travis/32/54079_2.png) [@Travis](https://discuss.elastic.co/u/Travis)\ **Post date:** [February 19, 2020, 11:10am UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946/1 "2020-02-19T11:10:56Z")
Hello there, After 7.6 upgrade, I noticed that the number of Kibana instance in Monitoring tab is not the good one. I checked that my 2 Kibana instance can join the cluster : it's OK. Monitoring still show only one Kibana instance on the two Do you know if there is something in particular to do or this would be a bug following the upgrade in 7.6 ? Thank you ! ๐Ÿ™‚ ---
**Author:** ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)\ **Post date:** [February 19, 2020, 7:40pm UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946/2 "2020-02-19T19:40:07Z")
I think I need a bit more information from you: how did you upgrade? Do both Kibana instances have a unique uuid? (You can find the uuid in the location of your `kibana.yml` `path.data`, default is a folder called `data`) Did any other settings change in kibana.yml? ---
**Author:** ![Travis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/travis/32/54079_2.png) [@Travis](https://discuss.elastic.co/u/Travis)\ **Post date:** [February 20, 2020, 4:39pm UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946/3 "2020-02-20T16:39:51Z")
Hello @wylie ! I upgraded all the Stack, ending by Kibana. I've just noticed that uuid are the same on the two Kibana ๐Ÿคจ ---
**Author:** ![Travis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/travis/32/54079_2.png) [@Travis](https://discuss.elastic.co/u/Travis)\ **Post date:** [February 21, 2020, 8:58am UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946/4 "2020-02-21T08:58:03Z")
Any way to generate a new uuid ? I tried to remove the string, then restart Kibana but it can't start after that..So it's not the good way to have a new uuid ---
**Author:** ![Travis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/travis/32/54079_2.png) [@Travis](https://discuss.elastic.co/u/Travis)\ **Post date:** [February 27, 2020, 12:57pm UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946/5 "2020-02-27T12:57:44Z")
@wylie do you know a way to retrieve a new uuid for one of the two instance ? ---
**Author:** ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)\ **Post date:** [February 27, 2020, 3:27pm UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946/6 "2020-02-27T15:27:30Z")
Yes, look at this section of the docs: [https://www.elastic.co/guide/en/kibana/current/production.html#load-balancing-kibana](https://www.elastic.co/guide/en/kibana/current/production.html#load-balancing-kibana) ---
**Author:** ![Travis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/travis/32/54079_2.png) [@Travis](https://discuss.elastic.co/u/Travis)\ **Post date:** [February 28, 2020, 7:56am UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946/7 "2020-02-28T07:56:57Z")
Hey @wylie ! Thanks for your feedback I followed your link which indicates to see the page [https://www.elastic.co/guide/en/kibana/7.6/settings.html](https://www.elastic.co/guide/en/kibana/7.6/settings.html) for settings but no mention of the setting "server.uuid" Finally I found a topic with the solution : stop kibana on one of the two Kibana server, remove /var/lib/kibana/uuid and restart. This will create a new uuid. So I think documentation can be updated to integrate this setting ๐Ÿ™‚ ---
**Author:** ![wylie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wylie/32/81794_2.png) [@wylie](https://discuss.elastic.co/u/wylie)\ **Post date:** [February 28, 2020, 4:40pm UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946/8 "2020-02-28T16:40:04Z")
@Travis I just learned about a bug in our packaging of 7.6.0 that you may be running into: [https://github.com/elastic/kibana/issues/57673](https://github.com/elastic/kibana/issues/57673) ---
**Author:** ![Travis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/travis/32/54079_2.png) [@Travis](https://discuss.elastic.co/u/Travis)\ **Post date:** [March 2, 2020, 8:55am UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946/9 "2020-03-02T08:55:15Z")
Yep good finding . This is exactly my issue. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 30, 2020, 8:55am UTC](https://discuss.elastic.co/t/kibana-7-6-reported-number-of-kibana-instance-is-false/219946/10 "2020-03-30T08:55:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.