logstash unexpectedly stopped


I have set up a logstash with redis architecture to handle my logs. The way I have organized it is:

logstash ---> redis ---> logstash ---> elasticsearch

but the problem that occurred is that after parsing nearly 1.25 million logs a java exception is thrown.

In my logstash.err log file, the exception appears as

Exception in thread "<file" java.lang.UnsupportedOperationException
    at java.lang.Thread.stop(Thread.java:869)
    at org.jruby.RubyThread.exceptionRaised(RubyThread.java:1221)
    at org.jruby.internal.runtime.RubyRunnable.run(RubyRunnable.java:112)
    at java.lang.Thread.run(Thread.java:745)

I think that this exception might be thrown because of logstash unable to open/close a file. So what can I do to rectify this error? The way that my input configuration is set for my first logstash server to send the logs is:

input {
    file {
        start_position => "beginning"
        path => [

And the way output is sent is like this:

output {
    redis {
        host => "X.X.X.X"
        key => "logstash"
        data_type => "list"

There are no errors in the logs of logstash server with redis installed.


Well, one problem here is with JRuby, which is trying to call Thread.stop(Throwable obj);, a deprecated method that throws UnsupportedOperationException and totally messes up the actual source of the error (the Throwable parameter).

So currently you can only guess what the actual problem is, and guessing is never good.

One idea is to set a breakpoint on RubyThread.exceptionRaised(); and run it through a debugger. That should allow you to find out what the original Throwable is, and then you can get to the source of the problem.

You should also check if there exists a bug ticket for JRuby about this, and possibly update your JRuby.

By : Kayaman

This video can help you solving your question :)
By: admin