# Self-induced error -deleted indeces

**URL:** <https://discuss.elastic.co/t/self-induced-error-deleted-indeces/292024>\
**Category:** Kibana\
**Created:** [December 15, 2021, 5:15pm UTC](https://discuss.elastic.co/t/self-induced-error-deleted-indeces/292024 "2021-12-15T17:15:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Orpheus](https://avatars.discourse-cdn.com/v4/letter/o/e36b37/32.png) [@Orpheus](https://discuss.elastic.co/u/Orpheus)\
**Post date:** [December 15, 2021, 5:15pm UTC](https://discuss.elastic.co/t/self-induced-error-deleted-indeces/292024/1 "2021-12-15T17:15:21Z")

</div>

Hi all,

rookie here again. Looking for some advice on this situation:

I just installed ELK with Filebeats about 3 weeks ago. Had a few modules running ok.

however, in three weeks I filled up the entire 700GB drive with logs, and everything stopped working.

My actions: manually deleted the indeces under the path.data source (not important log data to maintain, so I thought I would be ok here in order to free up the space)

updated the system as well as the software.

created an index lifecycle policy, so the data deletes after certain amount of time (14 days)

all patterns, config files are the same as before.

I was able to get the stack back up and running, (couldn't even access the API before) but none of the previous modules seem to be working. it appears that no new data is coming into kibana, and throws errors while trying to access indeces (likely because I deleted them)

any hints as to what I did/what I need to do to fix the modules?

Thanks

---

<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:** [December 20, 2021, 1:11am UTC](https://discuss.elastic.co/t/self-induced-error-deleted-indeces/292024/2 "2021-12-20T01:11:46Z")

</div>

> [@Orpheus](#):
>
> My actions: manually deleted the indeces under the path.data source

First up, _never_ do this again. It's going to cause all sorts of problems for Elasticsearch and everything that depends on it.  
**Always** use the APIs to manage this - [Delete index API | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-delete-index.html)

As for fixing things, we'd need to see the errors you see. But restarting Elasticsearch and then all the other parts of the stack might help.

---

<div class="post-metadata">

**Author:** ![Orpheus](https://avatars.discourse-cdn.com/v4/letter/o/e36b37/32.png) [@Orpheus](https://discuss.elastic.co/u/Orpheus)\
**Post date:** [December 20, 2021, 2:19pm UTC](https://discuss.elastic.co/t/self-induced-error-deleted-indeces/292024/3 "2021-12-20T14:19:54Z")

</div>

Hi Mark, thank you for the heads up. I wasn't able to access the API, so I didn't see any other recourse. Hence the result was to create a new machine and do a fresh install altogether. Which you appear to be helping me with on a different thread. Thanks again.

---

<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:** [January 17, 2022, 2:20pm UTC](https://discuss.elastic.co/t/self-induced-error-deleted-indeces/292024/4 "2022-01-17T14:20:27Z")

</div>

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