# Elastic Security inside Kibana periodically stops responding and requires a Kibana restart

**URL:** <https://discuss.elastic.co/t/elastic-security-inside-kibana-periodically-stops-responding-and-requires-a-kibana-restart/295273>\
**Category:** Kibana\
**Created:** [January 24, 2022, 7:09pm UTC](https://discuss.elastic.co/t/elastic-security-inside-kibana-periodically-stops-responding-and-requires-a-kibana-restart/295273 "2022-01-24T19:09:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kossde](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@kossde](https://discuss.elastic.co/u/kossde)\
**Post date:** [January 24, 2022, 7:09pm UTC](https://discuss.elastic.co/t/elastic-security-inside-kibana-periodically-stops-responding-and-requires-a-kibana-restart/295273/1 "2022-01-24T19:09:40Z")

</div>

We are on 7.13.2. At least once a day, access to Elastic Security breaks down. Other areas of Kibana continue to work (Dashboard, Dev tools, etc.) but the Security area loads to a blank screen. When I bring up Kibana's status, it's red and specifies that Task Manager is unavailable. Below is a segment of the Kibana status results. Any idea on what could be causing this and what the solution may be?

> plugin:lists@7.13.2  
> [security]: [taskManager]: Task Manager is unavailable  
> plugin:logstash@7.13.2  
> [2] services are unavailable  
> plugin:maps@7.13.2  
> [2] services are unavailable  
> plugin:monitoring@7.13.2  
> [7] services are unavailable  
> plugin:observability@7.13.2  
> [3] services are unavailable  
> plugin:osquery@7.13.2  
> [5] services are unavailable  
> plugin:remoteClusters@7.13.2  
> [2] services are unavailable  
> plugin:reporting@7.13.2  
> [security]: [taskManager]: Task Manager is unavailable  
> plugin:rollup@7.13.2  
> [indexManagement]: [2] services are unavailable  
> plugin:ruleRegistry@7.13.2  
> [2] services are unavailable  
> plugin:savedObjectsTagging@7.13.2  
> [security]: [taskManager]: Task Manager is unavailable  
> plugin:security@7.13.2  
> [taskManager]: Task Manager is unavailable

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 24, 2022, 10:52pm UTC](https://discuss.elastic.co/t/elastic-security-inside-kibana-periodically-stops-responding-and-requires-a-kibana-restart/295273/2 "2022-01-24T22:52:32Z")

</div>

What do the Kibana logs show?  
What about Elasticsearch?

---

<div class="post-metadata">

**Author:** ![kossde](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@kossde](https://discuss.elastic.co/u/kossde)\
**Post date:** [January 27, 2022, 9:31pm UTC](https://discuss.elastic.co/t/elastic-security-inside-kibana-periodically-stops-responding-and-requires-a-kibana-restart/295273/3 "2022-01-27T21:31:35Z")

</div>

Elasticsearch is fine, Kibana logs show a bunch of timed-out detections but nothing else. I converted a bunch of painless scripted runtime fields to normal fields and the issue hasn't returned, so maybe that was what was causing it.

---

<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:** [February 24, 2022, 9:32pm UTC](https://discuss.elastic.co/t/elastic-security-inside-kibana-periodically-stops-responding-and-requires-a-kibana-restart/295273/4 "2022-02-24T21:32:34Z")

</div>

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