NoMethodError after upgrading ELK stack

Hi all,

Just this past Thursday I upgraded our ELK stack from:

logstash-1.4.2-1
elasticsearch-1.3.2
Kibana 3

To:
logstash-2.3.0-1
elasticsearch-2.3.1
kibana-4.5.0-1

This was via local rpm installs since we are PCI compliant and thus don’t have internet access. Since that time, Logstash crashes shortly after startup with:

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:inexecute'", "/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:incall'", "/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:incall'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/task.rb:24:in `initialize'"], :level=>:warn}

I even pared down our configs to the bare minimum and still get the error:

input {
file {
path => "/site/syslog/log.all"
}
}

output {
elasticsearch {}
}

Does anyone have any suggestions?

Thanks in advance.

Please upgrade Logstash to 2.3.1, there were a few bugs with 2.3.0.

Mark,

That worked, thanks!