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

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'"]}

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

Someone help me ?
Thank!

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

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!

Something like puppet, ansible or other automation.

ah, no, i dont use any config management.

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