# Kibana - No Instances Running

**URL:** <https://discuss.elastic.co/t/kibana-no-instances-running/204263>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [October 18, 2019, 6:12pm UTC](https://discuss.elastic.co/t/kibana-no-instances-running/204263 "2019-10-18T18:12:26Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [October 21, 2019, 2:30pm UTC](https://discuss.elastic.co/t/kibana-no-instances-running/204263/7 "2019-10-21T14:30:11Z")

</div>

I've never seen it before, actually looking into it a bit more, that error _is_ from ES: eg [Elasticsearch 7.0.1 - Trying to create too many scroll contexts. Must be less than or equal to: [500]](https://discuss.elastic.co/t/elasticsearch-7-0-1-trying-to-create-too-many-scroll-contexts-must-be-less-than-or-equal-to-500/181687) .. so presumably your client was using up all the scroll contexts and via some unknown mechanism this caused errors in Kibana.

There isn't sufficient information logged currently to tell if that's related to the loss of availability of Kibana unfortunately. But at least this suggests that you might want to have a look into your client behavior?

---

_[View the full topic](https://discuss.elastic.co/t/kibana-no-instances-running/204263)._
