You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please post all product and debugging questions on our forum. Your questions will reach our wider community members there, and if we confirm that there is a bug, then we can open a new issue here.
For all general issues, please provide the following details for fast resolution:
Version: v4.2.1
Operating System: windows server 2012 R2
Config File (if you have sensitive info, please remove it):
Sample Data:
Steps to Reproduce:
when log rotation happens, same inode being used. After reading end of file(xx.log), when log rotation happens, it starts reading(xx.log.2020-10-dd - the file which got rotated). It supposed to read(xx.log file) but thats not happening.
when I delete sincedb file, stop and start logstash with start_position => beginning, the new inode is being generated and the entire records from xx.log is being sent to kafka.
Using logstash 7.9 with logstash-input-file v4.2.1.
This issue is mostly similar to what is mentioned here - #207
Please post all product and debugging questions on our forum. Your questions will reach our wider community members there, and if we confirm that there is a bug, then we can open a new issue here.
For all general issues, please provide the following details for fast resolution:
when log rotation happens, same inode being used. After reading end of file(xx.log), when log rotation happens, it starts reading(xx.log.2020-10-dd - the file which got rotated). It supposed to read(xx.log file) but thats not happening.
when I delete sincedb file, stop and start logstash with start_position => beginning, the new inode is being generated and the entire records from xx.log is being sent to kafka.
Using logstash 7.9 with logstash-input-file v4.2.1.
This issue is mostly similar to what is mentioned here - #207
Below is the config we use:
The text was updated successfully, but these errors were encountered: