# Failing to create index

**URL:** <https://discuss.elastic.co/t/failing-to-create-index/161336>\
**Category:** Elasticsearch\
**Created:** [December 18, 2018, 1:39pm UTC](https://discuss.elastic.co/t/failing-to-create-index/161336 "2018-12-18T13:39:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pk.241011](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pk.241011/32/86285_2.png) [@pk.241011](https://discuss.elastic.co/u/pk.241011)\
**Post date:** [December 18, 2018, 1:39pm UTC](https://discuss.elastic.co/t/failing-to-create-index/161336/1 "2018-12-18T13:39:15Z")

</div>

To be honest this seems to be an issue in Serilog which is still [open](https://github.com/serilog/serilog-sinks-elasticsearch/issues/140).

The Elasticsearch has been upgraded from 5.2.x to 6.5.2.

Suppose the existing index followed the naming pattern log-abc-2008.12. Now if I delete this index and then try to run the serilog, something strange happens. The index is not created. It is able to create log-ABCD-2018.

Is there some trace of old indices somewhere hidden in Elasticsearch or kibana. I will like to remove 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:** [January 15, 2019, 1:49pm UTC](https://discuss.elastic.co/t/failing-to-create-index/161336/2 "2019-01-15T13:49:02Z")

</div>

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