# How to run multiple conf file continusly in backend **URL:** \ **Category:** Logstash\ **Created:** [May 24, 2018, 6:41am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079 "2018-05-24T06:41:37Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![mamta](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@mamta](https://discuss.elastic.co/u/mamta)\ **Post date:** [May 24, 2018, 6:41am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/1 "2018-05-24T06:41:37Z")
Hey, I have installed ELK 5.6.8 version on Linux machine in a production environment. I have multiple conf files for each log.Currently I am running conf file from bin# ./logstash -f . I also tried to run from /etc/logstash/conf.d directory. I was tried to run conf file continuously by using nohup and crontab but at a time only one conf file is running continuously on the backend. Can you please help me to run conf file continuously on the backend. Thank you. ---
**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:** [May 24, 2018, 7:01am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/2 "2018-05-24T07:01:47Z")
How did you install Logstash? ---
**Author:** ![mamta](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@mamta](https://discuss.elastic.co/u/mamta)\ **Post date:** [May 24, 2018, 7:12am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/3 "2018-05-24T07:12:05Z")
Through rpm packages ---
**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:** [May 24, 2018, 7:12am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/4 "2018-05-24T07:12:28Z")
Then why not use service/systemctl? ---
**Author:** ![mamta](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@mamta](https://discuss.elastic.co/u/mamta)\ **Post date:** [May 24, 2018, 7:14am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/5 "2018-05-24T07:14:56Z")
I have used systemctl restart logstash , systemctl enable logstash, commands. But my question is how I can run logstash.conf file continuously in back-end. ---
**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:** [May 24, 2018, 7:16am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/6 "2018-05-24T07:16:19Z")
That's how you do it, if you put files in `/etc/logstash/conf.d/` then the process will start and run them continuously. If that is not happening, then perhaps you need to share a bit more info. ---
**Author:** ![mamta](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@mamta](https://discuss.elastic.co/u/mamta)\ **Post date:** [May 24, 2018, 7:24am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/7 "2018-05-24T07:24:47Z")
Hey, In /etc/logstash/conf.d directory I have kept only one conf file and I start logstash by using systemctl restart logstash but the file was not running at-least for once. Will it possible to run multiple conf file from this location? I have uploaded Apache error log conf file. ![conf](https://us1.discourse-cdn.com/elastic/original/3X/1/1/11f1e9f3d38900c2c3a3dc7d7a2253a9b7fe2079.png) Thank you. ---
**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:** [May 24, 2018, 7:29am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/8 "2018-05-24T07:29:07Z")
Please don't post pictures of text, they are difficult to read and some people may not be even able to see them 🙂 ---
**Author:** ![mamta](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@mamta](https://discuss.elastic.co/u/mamta)\ **Post date:** [May 24, 2018, 7:58am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/9 "2018-05-24T07:58:37Z")
Ok. Then how I can give you more info? ---
**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:** [May 24, 2018, 8:44pm UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/10 "2018-05-24T20:44:15Z")
Copy and paste the text. ---
**Author:** ![mamta](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@mamta](https://discuss.elastic.co/u/mamta)\ **Post date:** [May 25, 2018, 6:03am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/11 "2018-05-25T06:03:02Z")
Hey, In /etc/logstash/conf.d directory I have kept only one conf file and I start logstash by using systemctl restart logstash but the file was not running at-least for once. Will it possible to run multiple conf files from this location? I have uploaded my apache error log conf file. Please look into it @warkolm . input { file { path =\> "/var/log/httpd/error\_log" start\_position =\> "beginning" type =\> "logs" } } filter { grok { match =\> ["message", "(?[%{DAY} %{MONTH} %{MONTHDAY} %{TIME} %{YEAR}]) [%{GREEDYDATA:loglevel}] [%{GREEDYDATA:pid}] %{GREEDYDATA:errormsg} %{GREEDYDATA:path}" ] } } output { elasticsearch { hosts =\> ["localhost:9200"] index =\> "apache\_errorlog" } } ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 22, 2018, 6:03am UTC](https://discuss.elastic.co/t/how-to-run-multiple-conf-file-continusly-in-backend/133079/12 "2018-06-22T06:03:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.