Using email output causes crash if run as a daemon
Description
Gliffy Diagrams
Activity
Show:
Jens Schneider April 22, 2014 at 2:35 PM
Same problem here, Logstash 1.3.3 on RHEL 6.4.
Adam Gray March 18, 2014 at 7:06 PM
I've been running into this for the past day or two. Yes, it's still a problem in 1.3.3.
Jason Kendall March 5, 2014 at 4:44 PM
I could try it, but I'm just a community member trying to triage the 600+ JIRA tickets, and was hoping the OP or a watcher would have noticed if this is corrected already.
Tomas Doran March 5, 2014 at 4:35 PM
It's easy to test, why not try it?
I would expect so, unless you think something specific has changed which would correct this..
Jason Kendall March 5, 2014 at 3:58 PM
Is this still a problem in 1.3.3?
If I use the logstash email output, then it works fine if I start logstash from an interactive session.
However if I use start-stop-daemon to start logstash, then it crashes (with no helpful info whatsoever about what is going wrong).
From stracing the process, it seems that when started without an interactive environment, then something goes horribly wrong, and it starts doing things like:
[pid 16509] stat("/jar:file:/opt/logstash-monolithic.jar!/gems/mail-2.5.3/lib/mail/../VERSION", 0x7f77281e5dd0) = -1 ENOENT (No such file or directory
very shortly before aborting - note the leading slash.
I assume this is a jruby issue of some form / to do with JRUBY 6970 in some way - however I've not been able to work out any more details than that..