After upgrading to app-admin/logstash-bin-2.3.0, trying to run the init script results in this error message: # /etc/init.d/logstash start * Checking your configuration ... Sending logstash logs to /var/log/logstash/logstash.log. * Configuration error. Please fix your configuration files. [ !! ] * ERROR: logstash failed to start The log file (/var/log/logstash/logstash.log in this case) says: {:timestamp=>"2016-04-03T20:52:35.449000+0200", :message=>"An unexpected error occurred!", :error=>#<NoMethodError: undefined method `config_valid?' for LogStash::Pipeline:Class>, :class=>"NoMethodError", :backtrace=>["/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.0-java/lib/logstash/agent.rb:169:in `execute'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.0-java/lib/logstash/runner.rb:94:in `run'", "org/jruby/RubyProc.java:281:in `call'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.0-java/lib/logstash/runner.rb:99:in `run'", "org/jruby/RubyProc.java:281:in `call'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/task.rb:24:in `initialize'"], :level=>:warn} This has already been found and fixed upstream: https://github.com/elastic/logstash/issues/4933 The issue is that running in the "--configtest" mode doesn't work in 2.3.0. Since I knew I had a working config, I worked around the problem by changing the init script so that instead of running "${command} ${command_args} --configtest" the init script just runs "true". Since it seems 2.3.0 has no chance of working at all with Gentoo's init script, perhaps that version should be masked in anticipation of a fixed 2.3.1?
2.3.0 is masked for now, waiting for 2.3.1 release
2.3.1 in tree, thanks for reporting.
