# Clean install and running as a service: no files in /etc/logstash/conf.d/\*

**URL:** https://discuss.elastic.co/t/clean-install-and-running-as-a-service-no-files-in-etc-logstash-conf-d/97920
**Category:** Logstash
**Created:** [August 22, 2017, 2:00pm UTC](https://discuss.elastic.co/t/clean-install-and-running-as-a-service-no-files-in-etc-logstash-conf-d/97920 "2017-08-22T14:00:32Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Zilean](https://avatars.discourse-cdn.com/v4/letter/z/848f3c/32.png) [@Zilean](https://discuss.elastic.co/u/Zilean)
#### Post date: [August 22, 2017, 2:00pm UTC](https://discuss.elastic.co/t/clean-install-and-running-as-a-service-no-files-in-etc-logstash-conf-d/97920/1 "2017-08-22T14:00:32Z")

</div>

Hi,

I am setting up logstash 5.5.1 in a RHEL 7 and my java version is 1.8.0\_144 (Oracle).

I have been following the tutorials and it seems that the pipeline configuration files are placed in the /etc/logstash/conf.d directory. I have installed Logstash using the RPM and doing "yum -y localinstall logstash-5.5.1.rpm".

I have enabled the service using systemctl and It is running, however the log is reporting the following error: No config files found in path {:path=\>"/etc/logstash/conf.d/\*"}

This is happening because the conf.d directory is empty. So I tried to create some links in /etc/logstash/conf.d/ pointing to the configuration files stored in /etc/logstash/: jvm.options, log4j2.properties, logstash.yml, and startup.options.

If I do that, there is a new error:

[2017-08-22T15:38:22,078][ERROR][logstash.agent] Cannot create pipeline {:reason=\>"Expected one of #, input, filter, output at line 6, column 1 (byte 132) after ## JVM configuration\n\n# Xms represents the initial size of total heap space\n# Xmx represents the maximum size of total heap space\n\n"}

I am running out of ideas, how could I set up the configuration files properly?

Anyays, I have some questions:

- Why is Logstash taking the configuration files from conf.d instead of /etc/logstash/ (even if it is a service, why is not using those?)

- Is Logstash generating a mix of all the configuration in a single configuration file? Why is doing that?

- I am following this tutorial: [https://www.elastic.co/guide/en/logstash/5.5/installing-logstash.html](https://www.elastic.co/guide/en/logstash/5.5/installing-logstash.html) , am I missing any other tutorial?

---

<div class="post-metadata">

### Author: ![Vishal\_Sharma1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishal_sharma1/32/20207_2.png) [@Vishal\_Sharma1](https://discuss.elastic.co/u/Vishal_Sharma1)
#### Post date: [August 22, 2017, 2:04pm UTC](https://discuss.elastic.co/t/clean-install-and-running-as-a-service-no-files-in-etc-logstash-conf-d/97920/2 "2017-08-22T14:04:29Z")

</div>

create an empty file logstash.conf in /etc/logstash/conf.d and run logstash.

---

<div class="post-metadata">

### Author: ![mhgeay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mhgeay/32/21365_2.png) [@mhgeay](https://discuss.elastic.co/u/mhgeay)
#### Post date: [August 22, 2017, 2:21pm UTC](https://discuss.elastic.co/t/clean-install-and-running-as-a-service-no-files-in-etc-logstash-conf-d/97920/3 "2017-08-22T14:21:11Z")

</div>

Hello,

Vishal\_Sharma1's solution is the quick one 🙂

Your answers :

1. By default (Unix Deb), Logstash **core** conf is in /etct/logstash/ and logstash **pipeline** (what you do with processed data) conf is in /etc/logstash/conf.d. Like a web server (nginx/apache), you have the web server settings itself and the virtual host conf for one or more websites.
2. When you start Logstash process/service, it merge all pipeline conf files (conf.d/) into one file ; so be aware to use a single file or alphabetical filenames to be sure that logstash read your pipeline conf in the correct order. I don't know the reason....
3. It's the correct doc, but you seem confusing between core and pipeline confs.

---

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [August 23, 2017, 9:19pm UTC](https://discuss.elastic.co/t/clean-install-and-running-as-a-service-no-files-in-etc-logstash-conf-d/97920/5 "2017-08-23T21:19:55Z")

</div>

> When you start Logstash process/service, it merge all pipeline conf files (conf.d/) into one file ; so be aware to use a single file or alphabetical filenames to be sure that logstash read your pipeline conf in the correct order. I don’t know the reason…

How did you expect things to work?

---

<div class="post-metadata">

### Author: ![mhgeay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mhgeay/32/21365_2.png) [@mhgeay](https://discuss.elastic.co/u/mhgeay)
#### Post date: [August 23, 2017, 9:36pm UTC](https://discuss.elastic.co/t/clean-install-and-running-as-a-service-no-files-in-etc-logstash-conf-d/97920/6 "2017-08-23T21:36:42Z")

</div>

Hello Magnus,

I didn't expect anything, it simple and efficient for me, but there is maybe other best behaviour, I'm curious 🙂

---

<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: [September 20, 2017, 9:36pm UTC](https://discuss.elastic.co/t/clean-install-and-running-as-a-service-no-files-in-etc-logstash-conf-d/97920/7 "2017-09-20T21:36:59Z")

</div>

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