# Logstash Random Error
**URL:** https://discuss.elastic.co/t/logstash-random-error/69080
**Category:** Logstash
**Created:** [December 14, 2016, 8:18pm UTC](https://discuss.elastic.co/t/logstash-random-error/69080 "2016-12-14T20:18:13Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@chromechris](https://discuss.elastic.co/u/chromechris)
#### Post date: [December 14, 2016, 8:18pm UTC](https://discuss.elastic.co/t/logstash-random-error/69080/1 "2016-12-14T20:18:13Z")
I received this random error in my Logstash logs. My Logstash has been running fine, i'm not sure what could have caused this error.
{:timestamp=\>"2016-09-30T14:42:14.342000-0700", :message=\>"Exception in pipelineworker, the pipeline stopped processing new events, please check your filter configuration and restart Logstash.", "exception"=\>#\, "backtrace"=\>["org/jruby/RubyString.java:4462:in `include?'", "(eval):151:in`initialize'", "org/jruby/RubyArray.java:1613:in `each'", "(eval):149:in`initialize'", "org/jruby/RubyProc.java:281:in `call'", "(eval):167:in`initialize'", "org/jruby/RubyArray.java:1613:in `each'", "(eval):163:in`initialize'", "org/jruby/RubyProc.java:281:in `call'", "(eval):93:in`filter\_func'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:267:in `filter_batch'", "org/jruby/RubyArray.java:1613:in`each'", "org/jruby/RubyEnumerable.java:852:in `inject'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:265:in`filter\_batch'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:223:in `worker_loop'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:201:in`start\_workers'"], :level=\>:error}
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [December 15, 2016, 6:51am UTC](https://discuss.elastic.co/t/logstash-random-error/69080/2 "2016-12-15T06:51:58Z")
You log snippet has been mangled since you didn't post it as preformatted text. Specifically, `"exception"=>#` should be something like `"exception"=>#`. Also, what does your filter configuration look like?
---
### Author:  [@chromechris](https://discuss.elastic.co/u/chromechris)
#### Post date: [December 15, 2016, 3:48pm UTC](https://discuss.elastic.co/t/logstash-random-error/69080/3 "2016-12-15T15:48:07Z")
My bad, here it is in preformatted text :
`{:timestamp=>"2016-09-30T14:42:14.342000-0700", :message=>"Exception in pipelineworker, the pipeline stopped processing new events, please check your filter configuration and restart Logstash.", "exception"=>#, "backtrace"=>["org/jruby/RubyString.java:4462:in`include?'", "(eval):151:in `initialize'", "org/jruby/RubyArray.java:1613:in`each'", "(eval):149:in `initialize'", "org/jruby/RubyProc.java:281:in`call'", "(eval):167:in `initialize'", "org/jruby/RubyArray.java:1613:in`each'", "(eval):163:in `initialize'", "org/jruby/RubyProc.java:281:in`call'", "(eval):93:in `filter_func'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:267:in`filter\_batch'", "org/jruby/RubyArray.java:1613:in `each'", "org/jruby/RubyEnumerable.java:852:in`inject'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:265:in `filter_batch'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:223:in`worker\_loop'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:201:in `start_workers'"], :level=>:error}`
I guess it found an empty string. Maybe that was the case, since it is giving the error of "can't convert nil into String". My configuration is a bit messy to look at since I have multiple Input/ filter files and one output file.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 12, 2017, 3:48pm UTC](https://discuss.elastic.co/t/logstash-random-error/69080/4 "2017-01-12T15:48:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.