# Logstash 2.3.0 Startup Error **URL:** \ **Category:** Logstash\ **Created:** [April 4, 2016, 10:35am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225 "2016-04-04T10:35:57Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![Sameer\_Dharur](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@Sameer\_Dharur](https://discuss.elastic.co/u/Sameer_Dharur)\ **Post date:** [April 4, 2016, 10:35am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/1 "2016-04-04T10:35:57Z")
Hello! I had been using this configuration for Logstash 2.2.0 until this morning, which worked perfectly. But after an upgrade to 2.3.0, I get the following error message on the console - An unexpected error occurred! {:error=\>#\, :class=>"NoMethodError", :backtrace=>["/home/bits/logstash-2.3.0/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.0-java/lib/logstash/agent.rb:169:in`execute'", "/home/bits/logstash-2.3.0/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'", "/home/bits/logstash-2.3.0/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'", "/home/bits/logstash-2.3.0/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/task.rb:24:in `initialize'"], :level=\>:warn} Here's my config file - input { file { path =\> "/home/bits/Server\_Code/TempLight.log" type =\> "sample" start\_position =\> "beginning" } } filter { grok { match =\> { "message" =\> "%{DAY:day}\s%{MONTH:month}\s%{MONTHDAY:monthday}\s%{YEAR:year}\s%{TIME:time}\sGMT(?[+-]\d\d\d\d)\s([^)]+)\s%{NUMBER:temp}\s%{NUMBER:light}\s%{GREEDYDATA:room}"} } } output { elasticsearch { index =\> "logstash-templightlogs" } stdout{} } ---
**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 4, 2016, 11:23pm UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/2 "2016-04-04T23:23:43Z")
Is that all the error was? ---
**Author:** ![Sameer\_Dharur](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@Sameer\_Dharur](https://discuss.elastic.co/u/Sameer_Dharur)\ **Post date:** [April 5, 2016, 1:51am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/3 "2016-04-05T01:51:09Z")
Yes, that was all. ---
**Author:** ![Sameer\_Dharur](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@Sameer\_Dharur](https://discuss.elastic.co/u/Sameer_Dharur)\ **Post date:** [April 5, 2016, 8:41am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/4 "2016-04-05T08:41:18Z")
I tried the same config on Logstash 2.2.3 as opposed to Logstash 2.3.0 and here's the error I'm seeing on the console. ![](https://us1.discourse-cdn.com/elastic/original/2X/5/55d0961d69940b6e3db659c019ec0100c12313d6.png) ---
**Author:** ![Sameer\_Dharur](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@Sameer\_Dharur](https://discuss.elastic.co/u/Sameer_Dharur)\ **Post date:** [April 5, 2016, 8:53am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/5 "2016-04-05T08:53:57Z")
Update : I hosted Elasticsearch publicly on '172.25.3.31' and port '9200'. So I updated my Logstash config to reflect this. Now I see Logstash Startup Completed with no errors but I don't see any of the logs in the console, which means they aren't going through to the ES server. Here's the config file - input { file { path =\> "/home/bits/Server\_Code/TempLight.log" type =\> "sample" start\_position =\> "beginning" } } filter { grok { match =\> { "message" =\> "%{DAY:day}\s%{MONTH:month}\s%{MONTHDAY:monthday}\s%{YEAR:year}\s%{TIME:time}\sGMT(?[+-]\d\d\d\d)\s([^)]+)\s%{NUMBER:temp}\s%{NUMBER:light}\s%{GREEDYDATA:room}"} } } output { elasticsearch { index =\> "logstash-templightlogs" hosts =\> "172.25.3.31:9200" } stdout{} } ---
**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 5, 2016, 9:16am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/6 "2016-04-05T09:16:01Z")
I think this might be a known issue we are working on fixing. Try downgrading to 2.2.X and see if you get it. ---
**Author:** ![Sameer\_Dharur](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@Sameer\_Dharur](https://discuss.elastic.co/u/Sameer_Dharur)\ **Post date:** [April 5, 2016, 10:20am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/7 "2016-04-05T10:20:15Z")
I tried this on Logstash 2.2.3 as well. Same issue. It says "Logstash startup completed" but nothing after that. Anything I can change in my config? ---
**Author:** ![Sameer\_Dharur](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@Sameer\_Dharur](https://discuss.elastic.co/u/Sameer_Dharur)\ **Post date:** [April 5, 2016, 10:18am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/8 "2016-04-05T10:18:55Z")
Yes, I have tried this on Logstash 2.2.3 as well. Same error. Anything I can change in my config? ---
**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 5, 2016, 8:37pm UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/9 "2016-04-05T20:37:11Z")
Ah see I didn't open the image because they are usually too hard to read. It'd better if you post the text of console output like that, not the picture 🙂 What you are seeing is normal, it means LS has started and is waiting on new data in the file you specified in the input. This is not an error. ---
**Author:** ![Sameer\_Dharur](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@Sameer\_Dharur](https://discuss.elastic.co/u/Sameer_Dharur)\ **Post date:** [April 6, 2016, 3:37am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/10 "2016-04-06T03:37:03Z")
"Connection refused {:class=\>"Manticore::SocketException", :level=\>:error}" is what the console says for Logstash-2.3.0. The same line is repeated 8 times for Logstash-2.2.3. My config file is as follows - input { file { path =\> "/home/bits/Server\_Code/TempLight.log" type =\> "sample" start\_position =\> "beginning" sincedb\_path =\> "/home/bits/logstash-2.3.0/file" } } filter { grok { match =\> { "message" =\> "%{DAY:day}\s%{MONTH:month}\s%{MONTHDAY:monthday}\s%{YEAR:year}\s%{TIME:time}\sGMT(?[+-]\d\d\d\d)\s([^)]+)\s%{NUMBER:temp}\s%{NUMBER:light}\s%{GREEDYDATA:room}"} } } output { elasticsearch { index =\> "logstash-templightlogs" hosts =\> "172.25.3.31:9200" } stdout{} } ---
**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 6, 2016, 3:38am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/11 "2016-04-06T03:38:31Z")
Hosts is an array, so I'd fix that. Make sure you can connect to ES from the LS host too. ---
**Author:** ![Sameer\_Dharur](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@Sameer\_Dharur](https://discuss.elastic.co/u/Sameer_Dharur)\ **Post date:** [April 6, 2016, 8:32am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/12 "2016-04-06T08:32:18Z")
Right, so I've made hosts an array like you said. I must say here that I did not need to mention the hosts parameter when I was using Logstash-2.2.0 until two days ago. I'm surprised it is needed here. I see the following on my console - Settings: Default pipeline workers: 8 Pipeline main started However, none of the logs are actually getting stashed after this as is supposed to happen. Pasting my config file again here below - input { file { path =\> "/home/bits/Server\_Code/TempLight.log" type =\> "sample" start\_position =\> "beginning" sincedb\_path =\> "/home/bits/logstash-2.3.0/files" } } filter { grok { match =\> { "message" =\> "%{DAY:day}\s%{MONTH:month}\s%{MONTHDAY:monthday}\s%{YEAR:year}\s%{TIME:time}\sGMT(?[+-]\d\d\d\d)\s([^)]+)\s%{NUMBER:temp}\s%{NUMBER:light}\s%{GREEDYDATA:room}"} } } output { elasticsearch { index =\> "logstash-templightlogs" hosts =\> ['172.25.3.31:9200'] } stdout{} } ---
**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 6, 2016, 9:04am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/13 "2016-04-06T09:04:12Z")
Then it's probably a sincedb issue, have you delete the old ones? > [@Sameer\_Dharur](#): > > I'm surprised it is needed here. It's in the docs, has been for a while! ---
**Author:** ![Sameer\_Dharur](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@Sameer\_Dharur](https://discuss.elastic.co/u/Sameer_Dharur)\ **Post date:** [April 6, 2016, 9:44am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/14 "2016-04-06T09:44:58Z")
Got it running with Logstash-2.2.2. No sweat. Even deletion of the old ones did not help with the newer versions of Logstash. ---
**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:03am UTC](https://discuss.elastic.co/t/logstash-2-3-0-startup-error/46225/15 "2017-07-06T05:03:33Z")