Jordan Sissel

@nipunarora What exception? Can you show me a stack trace?

The exception message being '63' is ... confusing me. You'll have to modify the code to get a stack trace. Line 332 of logstash/filters/grok.rb is what prints the log message...

If you still experience this on newer releases of Logstash, can you provide a sample config and a sample input text that triggers the exception?

I propose two changes: 1) make "development" mode prompting yes/no to accept a server's certificate instead of blanket trusting everything. Prior art: SSH does this and is itself a wildly...

@michaelklishin I am conflating issues, sorry. My suggestion was unclear in scope and that my recommendation is to make it harder to disable trust, which includes not making it disabled...

I haven't confirmed if this is still a bug, but I agree about the problem. Logstash should somehow detect that the file being watched is on a remote filesystem _or_...

This problem should only exist if users are specifying the sincedb path themselves. The default (where no sincedb path is set) will likely avoid collision with other file inputs. I...

@jsvd +1 to having a warning and using flock (and later, maybe, some shared structure in Logstash to fail startup if conflicts are found)

This is likely due to the fact that Logstash will only look for new files when it reaches the end of the current file. In this scenario, the script is...

> Any news/progress on this one? @LionelCons I need more details if you want a good answer. I don't know what progress you are asking about. If you believe you...