# No config files found in path after 2-3 days uptime

**URL:** <https://discuss.elastic.co/t/no-config-files-found-in-path-after-2-3-days-uptime/93100>\
**Category:** Logstash\
**Created:** [July 14, 2017, 1:44am UTC](https://discuss.elastic.co/t/no-config-files-found-in-path-after-2-3-days-uptime/93100 "2017-07-14T01:44:32Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)\
**Post date:** [July 14, 2017, 1:44am UTC](https://discuss.elastic.co/t/no-config-files-found-in-path-after-2-3-days-uptime/93100/1 "2017-07-14T01:44:32Z")

</div>

I'm using Elastic stack 5.5, OS Centos 7 and testing with x-pack.

My logstash start normaly, no problem when started. But after 2-3 days update, i got error and logstash can't send data.

> [2017-07-14T08:31:39,747][INFO][logstash.agent] No config files found in path {:path=\>"/etc/logstash/conf.d/\*"}  
> [2017-07-14T08:31:39,747][ERROR][logstash.agent] An unexpected error occurred! {:message=\>"No config files found: /etc/logstash/conf.d/. Can you make sure this path is a logstash config file?", :class=\>"RuntimeError", :backtrace=\>["/usr/share/logstash/logstash-core/lib/logstash/config/loader.rb:18:in `format_config'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:294:in `fetch\_config'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:302:in `reload_pipeline!'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:111:in `reload\_state!'", "org/jruby/RubyHash.java:1342:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:108:in `reload\_state!'", "org/jruby/ext/thread/Mutex.java:149:in `synchronize'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:107:in `reload\_state!'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:75:in `execute'", "org/jruby/RubyProc.java:281:in `call'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/interval.rb:20:in `interval'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:75:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:321:in `execute'", "org/jruby/RubyProc.java:281:in `call'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/task.rb:24:in `initialize'"]}

 ![](https://us1.discourse-cdn.com/elastic/original/3X/d/3/d33b6c86cf1ae77a720f155363a8bc3775ad5ed2.png)

I'm running logstash instance with command

> /usr/share/logstash/bin/logstash --path.settings=/etc/logstash -b 1200 -w 6 -f /etc/logstash/conf.d/ --config.reload.automatic &

What happen ?. This error appear from version 5.4.3 in 2/5 logstash server (collector).  
NOTE: I have 5 logstash server: 3 collector, 2 proccessor

---

<div class="post-metadata">

**Author:** ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)\
**Post date:** [July 17, 2017, 1:05am UTC](https://discuss.elastic.co/t/no-config-files-found-in-path-after-2-3-days-uptime/93100/2 "2017-07-17T01:05:30Z")

</div>

Someone help me ?  
Thank!

---

<div class="post-metadata">

**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:** [July 17, 2017, 1:17am UTC](https://discuss.elastic.co/t/no-config-files-found-in-path-after-2-3-days-uptime/93100/3 "2017-07-17T01:17:00Z")

</div>

Do the config files still exist on the filesystem when this happens?  
Do you have some kind of config management happening?

---

<div class="post-metadata">

**Author:** ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)\
**Post date:** [July 17, 2017, 1:22am UTC](https://discuss.elastic.co/t/no-config-files-found-in-path-after-2-3-days-uptime/93100/4 "2017-07-17T01:22:55Z")

</div>

> Do the config files still exist on the filesystem when this happens?

Sure, config file still exitts on config folder

> Do you have some kind of config management happening?

I dont understand.. What do u you mean ?

Thanks!

---

<div class="post-metadata">

**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:** [July 17, 2017, 1:24am UTC](https://discuss.elastic.co/t/no-config-files-found-in-path-after-2-3-days-uptime/93100/5 "2017-07-17T01:24:28Z")

</div>

Something like puppet, ansible or other automation.

---

<div class="post-metadata">

**Author:** ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)\
**Post date:** [July 17, 2017, 1:28am UTC](https://discuss.elastic.co/t/no-config-files-found-in-path-after-2-3-days-uptime/93100/6 "2017-07-17T01:28:18Z")

</div>

> [@warkolm](#):
>
> ke puppet, ansible or other a

ah, no, i dont use any config management.

---

<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:** [August 14, 2017, 1:28am UTC](https://discuss.elastic.co/t/no-config-files-found-in-path-after-2-3-days-uptime/93100/7 "2017-08-14T01:28:46Z")

</div>

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