# Logstash 5 not running

**URL:** https://discuss.elastic.co/t/logstash-5-not-running/64449
**Category:** Logstash
**Created:** [October 31, 2016, 1:20pm UTC](https://discuss.elastic.co/t/logstash-5-not-running/64449 "2016-10-31T13:20:40Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [November 1, 2016, 8:36pm UTC](https://discuss.elastic.co/t/logstash-5-not-running/64449/16 "2016-11-01T20:36:28Z")

</div>

We have a potential fix to allow `-e` to still be used: create an empty file in `/etc/logstash/conf.d`. Call it whatever you like, e.g.

```auto
sudo touch /etc/logstash/conf.d/empty.conf

```

Even though the file is empty, it should prevent this error:

> [@Vishal\_Sharma1](#):
>
> [2016-11-01T12:39:45,739][ERROR][logstash.agent] failed to fetch pipeline configuration {:message=\>"No config files found: /etc/logstash/conf.d/\*\nCan you make sure this path is a logstash config file?"}

Should this work for those trying to use `-e` to do the test config in the docs, we will put an empty config file in /etc/logstash/conf.d in future package releases.

@Vishal_Sharma1

> [@Vishal\_Sharma1](#):
>
> 1. There is no mention about path.settings in official doc.

It's [right here](https://www.elastic.co/guide/en/logstash/5.0/breaking-changes.html#_application_settings) in the [breaking changes documentation](https://www.elastic.co/guide/en/logstash/5.0/breaking-changes.html).

---

_[View the full topic](https://discuss.elastic.co/t/logstash-5-not-running/64449)._