# Kibana monitoring issues with task not found

**URL:** <https://discuss.elastic.co/t/kibana-monitoring-issues-with-task-not-found/356403>\
**Category:** Kibana\
**Created:** [March 28, 2024, 2:10pm UTC](https://discuss.elastic.co/t/kibana-monitoring-issues-with-task-not-found/356403 "2024-03-28T14:10:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Maxime\_Beaudry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maxime_beaudry/32/123579_2.png) [@Maxime\_Beaudry](https://discuss.elastic.co/u/Maxime_Beaudry)\
**Post date:** [March 28, 2024, 2:10pm UTC](https://discuss.elastic.co/t/kibana-monitoring-issues-with-task-not-found/356403/1 "2024-03-28T14:10:30Z")

</div>

Currently working out some issues on our ELK deployment related to data loss and corrupted snapshots. I've since fixed the snapshot but previous ones are essentially lost.

Now, for context, we've had to remove the `data_content` role from some machines. We did not go through the documented steps and ran `elasticsearch-node repurpose` to delete the unwanted indices. We had thought at the time that restoring snapshots was the way we'd restore them, but turns out they were corrupted. Now we're trying in the short term to restore all functionality and learn from our mistakes.

Current issue is, stack monitoring isn't working in kibana due to a large number of `task not found` errors.

 ![Screenshot 2024-03-27 at 7.54.54 PM](https://us1.discourse-cdn.com/elastic/original/3X/b/3/b32b8577c25b13d501bb235eefaebb3e945ea093.jpeg)

I don't know where to go from here. Task indices are probably missing, but restarting the elastic cluster and kibana doesn't lead to a working state. Is there anything I should be cleaning up, or configuring otherwise?

---

<div class="post-metadata">

**Author:** ![Maxime\_Beaudry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maxime_beaudry/32/123579_2.png) [@Maxime\_Beaudry](https://discuss.elastic.co/u/Maxime_Beaudry)\
**Post date:** [April 2, 2024, 9:22pm UTC](https://discuss.elastic.co/t/kibana-monitoring-issues-with-task-not-found/356403/2 "2024-04-02T21:22:48Z")

</div>

Any idea? I was thinking about creating another cluster, taking a snapshot then restoring all of the kibana indices, but I don't know if this is a good idea. If it's got potential, what would be the indices to restore?

---

<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:** [April 30, 2024, 9:22pm UTC](https://discuss.elastic.co/t/kibana-monitoring-issues-with-task-not-found/356403/3 "2024-04-30T21:22:53Z")

</div>

Closed on April 30, 2024, 9:22pm UTC

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