# Pipeline is running but index is not created at elasticsearch

**URL:** https://discuss.elastic.co/t/pipeline-is-running-but-index-is-not-created-at-elasticsearch/333940
**Category:** Logstash
**Created:** [May 21, 2023, 10:27am UTC](https://discuss.elastic.co/t/pipeline-is-running-but-index-is-not-created-at-elasticsearch/333940 "2023-05-21T10:27:54Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [May 22, 2023, 6:07pm UTC](https://discuss.elastic.co/t/pipeline-is-running-but-index-is-not-created-at-elasticsearch/333940/13 "2023-05-22T18:07:36Z")

</div>

@Yasser_Alsawy I would suggest enabling TRACE level logging. The filewatch library that the file input uses will then [log](https://discuss.elastic.co/t/logstash-wildcards-regex-not-working/164204/2) when it finds the file and whether it sees any unread data in it.

In theory using /dev/null on WSL was fixed to work properly back in 2016 (as you might expect, a non-working /dev/null broke a lot of things), but if the trace logs indicate it has already read the file then try changing the sincedb\_path.

---

_[View the full topic](https://discuss.elastic.co/t/pipeline-is-running-but-index-is-not-created-at-elasticsearch/333940)._