Logstash - org.jruby.exceptions.SystemExit: (SystemExit) exit

Hi Team,

  • tried to create one logstash instance from the existing ( with same user data like the other one) but weird message when starting the logstash, details are as below,
    Could you please help me out with the fix

Feb 21 18:01:39 ip-10-33-160-248 logstash: [2022-02-21T18:01:39,967][INFO ][logstash.runner ] Log4j configuration path used is: /etc/logstash/log4j2.properties
Feb 21 18:01:40 ip-10-33-160-248 logstash: [2022-02-21T18:01:39,998][INFO ][logstash.runner ] Starting Logstash {"logstash.version"=>"7.17.0", "jruby.version"=>"jruby 9.2.20.1 (2.5.8) 2021-11-30 2a2962fbd1 OpenJDK 64-Bit Server VM 11.0.13+8 on 11.0.13+8 +indy +jit [linux-x86_64]"}
Feb 21 18:01:40 ip-10-33-160-248 logstash: [2022-02-21T18:01:40,010][INFO ][logstash.runner ] JVM bootstrap flags: [-Xms6g, -Xmx6g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djruby.compile.invokedynamic=true, -Djruby.jit.threshold=0, -Djruby.regexp.interruptible=true, -XX:+HeapDumpOnOutOfMemoryError, -Djava.security.egd=file:/dev/urandom, -Dlog4j2.isThreadContextMapInheritable=true]
Feb 21 18:01:40 ip-10-33-160-248 logstash: [2022-02-21T18:01:40,897][FATAL][logstash.runner ] An unexpected error occurred! {:error=>#<ArgumentError: wrong number of arguments (given 3, expected 1..2)>, :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/api/modules/base.rb:43:in initialize'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/sinatra-2.2.0/lib/sinatra/base.rb:1537:in new'", "/usr/share/logstash/logstash-core/lib/logstash/api/rack_app.rb:113:in block in app'", "org/jruby/RubyBasicObject.java:2622:in instance_eval'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/rack-2.2.3/lib/rack/builder.rb:125:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/api/rack_app.rb:101:in app'", "/usr/share/logstash/logstash-core/lib/logstash/webserver.rb:123:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/webserver.rb:74:in from_settings'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:76:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:520:in create_agent'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:411:in execute'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/clamp-1.0.1/lib/clamp/command.rb:68:in run'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:292:in run'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/clamp-1.0.1/lib/clamp/command.rb:133:in run'", "/usr/share/logstash/lib/bootstrap/environment.rb:93:in `'"]}
Feb 21 18:01:40 ip-10-33-160-248 logstash: [2022-02-21T18:01:40,906][FATAL][org.logstash.Logstash ] Logstash stopped processing because of an error: (SystemExit) exit
Feb 21 18:01:40 ip-10-33-160-248 logstash: org.jruby.exceptions.SystemExit: (SystemExit) exit
Feb 21 18:01:40 ip-10-33-160-248 logstash: at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:747) ~[jruby-complete-9.2.20.1.jar:?]
Feb 21 18:01:40 ip-10-33-160-248 logstash: at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:710) ~[jruby-complete-9.2.20.1.jar:?]
Feb 21 18:01:40 ip-10-33-160-248 logstash: at usr.share.logstash.lib.bootstrap.environment.(/usr/share/logstash/lib/bootstrap/environment.rb:94) ~[?:?]
Feb 21 18:01:40 ip-10-33-160-248 systemd: logstash.service: main process exited, code=exited, status=1/FAILURE
Feb 21 18:01:40 ip-10-33-160-248 systemd: Unit logstash.service entered failed state.
Feb 21 18:01:40 ip-10-33-160-248 systemd: logstash.service failed.
Feb 21 18:01:41 ip-10-33-160-248 systemd: logstash.service holdoff time over, scheduling restart.
Feb 21 18:01:41 ip-10-33-160-248 systemd: Stopped logstash.
Feb 21 18:01:41 ip-10-33-160-248 systemd: Started logstash.

There are multiple recent threads about this. See here. A logstash release that incorporates the fix may occur within a month, a fix to the Sinatra module that it uses may or may not occur earlier.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.