# NoMethodError after upgrading ELK stack

**URL:** <https://discuss.elastic.co/t/nomethoderror-after-upgrading-elk-stack/47146>\
**Category:** Logstash\
**Created:** [April 12, 2016, 4:00pm UTC](https://discuss.elastic.co/t/nomethoderror-after-upgrading-elk-stack/47146 "2016-04-12T16:00:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Mullay](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@Michael\_Mullay](https://discuss.elastic.co/u/Michael_Mullay)\
**Post date:** [April 12, 2016, 4:00pm UTC](https://discuss.elastic.co/t/nomethoderror-after-upgrading-elk-stack/47146/1 "2016-04-12T16:00:03Z")

</div>

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: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}

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.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 13, 2016, 1:44am UTC](https://discuss.elastic.co/t/nomethoderror-after-upgrading-elk-stack/47146/2 "2016-04-13T01:44:31Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Michael\_Mullay](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@Michael\_Mullay](https://discuss.elastic.co/u/Michael_Mullay)\
**Post date:** [April 13, 2016, 8:28pm UTC](https://discuss.elastic.co/t/nomethoderror-after-upgrading-elk-stack/47146/3 "2016-04-13T20:28:58Z")

</div>

Mark,

That worked, thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 5:02am UTC](https://discuss.elastic.co/t/nomethoderror-after-upgrading-elk-stack/47146/4 "2017-07-06T05:02:26Z")

</div>