# Bug logstash

**URL:** <https://discuss.elastic.co/t/bug-logstash/82186>\
**Category:** Logstash\
**Created:** [April 12, 2017, 3:42pm UTC](https://discuss.elastic.co/t/bug-logstash/82186 "2017-04-12T15:42:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![zak](https://avatars.discourse-cdn.com/v4/letter/z/8e7dd6/32.png) [@zak](https://discuss.elastic.co/u/zak)\
**Post date:** [April 12, 2017, 3:42pm UTC](https://discuss.elastic.co/t/bug-logstash/82186/1 "2017-04-12T15:42:10Z")

</div>

hi,  
when I launch logstash configuration.

input {  
file {  
path =\> "/elasticsearch/data/elastic\_stack/logstash-2.4.0/projects.csv"  
start\_position =\> "beginning"}}  
filter {  
xml {source =\> "message"}}  
output{  
stdout { codec =\> rubydebug }  
elasticsearch { hosts =\> "elasticsearch"  
protocol=\> http  
cluster =\> zakaria  
port =\> 9201  
index=\> "service\_index"}}

I had this error:  
Settings: Default pipeline workers: 2  
Pipeline aborted due to error {:exception=\>"LogStash::ConfigurationError", :backtrace=\>["/elasticsearch/data/elastic\_stack/logstash-2.4.0/vendor/bundle/jruby/1.9/gems/log  
stash-core-2.4.0-java/lib/logstash/config/mixin.rb:88:in `config_init'", "org/jruby/RubyHash.java:1342:in`each'", "/elasticsearch/data/elastic\_stack/logstash-2.4.0/vendo  
r/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/config/mixin.rb:72:in `config_init'", "/elasticsearch/data/elastic_stack/logstash-2.4.0/vendor/bundle/jruby/ 1.9/gems/logstash-core-2.4.0-java/lib/logstash/outputs/base.rb:79:in`initialize'", "/elasticsearch/data/elastic\_stack/logstash-2.4.0/vendor/bundle/jruby/1.9/gems/logstas  
h-core-2.4.0-java/lib/logstash/output\_delegator.rb:74:in `register'", "/elasticsearch/data/elastic_stack/logstash-2.4.0/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-j ava/lib/logstash/pipeline.rb:181:in`start\_workers'", "org/jruby/RubyArray.java:1613:in `each'", "/elasticsearch/data/elastic_stack/logstash-2.4.0/vendor/bundle/jruby/1.9 /gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:181:in`start\_workers'", "/elasticsearch/data/elastic\_stack/logstash-2.4.0/vendor/bundle/jruby/1.9/gems/logstash-c  
ore-2.4.0-java/lib/logstash/pipeline.rb:136:in `run'", "/elasticsearch/data/elastic_stack/logstash-2.4.0/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstas h/agent.rb:491:in`start\_pipeline'"], :level=\>:error}  
stopping pipeline {:id=\>"main"}

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [April 12, 2017, 3:46pm UTC](https://discuss.elastic.co/t/bug-logstash/82186/2 "2017-04-12T15:46:05Z")

</div>

There's a known bug in Logstash 2.4.0 that hides the actual error message. I suggest you upgrade so you can see what it's really complaining over.

---

<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:** [May 10, 2017, 3:50pm UTC](https://discuss.elastic.co/t/bug-logstash/82186/3 "2017-05-10T15:50:50Z")

</div>

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