I have this issue with a conf file. I create the file and start laying out a filter. I then save and test it, everything is going well. Then ill add something like another grok filter, add a tag, or overwrite a field. Ill restart the service and the new additions will not work. Ill walk away for a few hours and come back and it starts working. This doesn't happen on all my conf files just a few. This one and another i was working on a few weeks ago. It seems like logstash is using a cached version of the config. I know this because ill deliberately put a typo in the new section of the file and it will still load without error.
Is there some type of .conf file cache setting that will hold on to an old version of the config?
Thanks for the help in advance. This one is really driving me crazy
How are you running logstash, i.e. daemon on Centos for example?
Can you post the contents of /etc/logstash/conf.d or your path you use for config?
Can you explain this: "I know this because ill deliberately put a typo in the new section of the file and it will still load without error." - this is weird. If the config is syntax(ly?) correct then the server will not start it...
Its a service on ubuntu 16.04.5.
Below is a config i am working on. The path is /etc/logstash/conf.d/
Remember that this doesn't do this to all my configs. Just a select few like the one below. I have config reload interval set to 5s and ive noticed when i change this file, logstash doesn't reload. I have to restart the service, leave it be for a few hours and then it starts working. I have tried deleting the file and starting over but same result.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.