# Logstash start/killed

**URL:** <https://discuss.elastic.co/t/logstash-start-killed/104225>\
**Category:** Logstash\
**Created:** [October 17, 2017, 10:39am UTC](https://discuss.elastic.co/t/logstash-start-killed/104225 "2017-10-17T10:39:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mayotte](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mayotte/32/24914_2.png) [@Mayotte](https://discuss.elastic.co/u/Mayotte)\
**Post date:** [October 17, 2017, 10:39am UTC](https://discuss.elastic.co/t/logstash-start-killed/104225/1 "2017-10-17T10:39:04Z")

</div>

Hello,

Logstash stop to work. It not possible now to start or stop.

And the initctl status logstash command show :  
logstash start/killed, process 3627  
But not PID, impossible to start/restart/stop

Logstash version 5.6.3  
CentOS 6.8

Any ideas ?

Thanks

---

<div class="post-metadata">

**Author:** ![Mayotte](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mayotte/32/24914_2.png) [@Mayotte](https://discuss.elastic.co/u/Mayotte)\
**Post date:** [October 18, 2017, 10:17am UTC](https://discuss.elastic.co/t/logstash-start-killed/104225/2 "2017-10-18T10:17:52Z")

</div>

when I run /usr/share/logstash/bin/logstash --path.settings /etc/logstash :

[2017-10-17T16:55:31,504][WARN][logstash.codecs.netflow] Can't (yet) decode flowset id 261 from source id 0, because no template to decode it with has been received. This message will usually go away after 1 minute.  
[2017-10-17T16:55:31,504][WARN][logstash.codecs.netflow] Can't (yet) decode flowset id 265 from source id 0, because no template to decode it with has been received. This message will usually go away after 1 minute.  
[2017-10-17T16:55:31,646][WARN][logstash.codecs.netflow] Can't (yet) decode flowset id 265 from source id 0, because no template to decode it with has been received. This message will usually go away after 1 minute.  
[2017-10-17T16:55:36,288][ERROR][logstash.pipeline] Exception in pipelineworker, the pipeline stopped processing new events, please check your filter configuration and restart Logstash. {"exception"=\>"undefined method `<' for nil:NilClass", "backtrace"=>["(eval):704:in`initialize'", "org/jruby/RubyArray.java:1613:in `each'", "(eval):702:in`initialize'", "org/jruby/RubyProc.java:281:in `call'", "(eval):722:in`initialize'", "org/jruby/RubyArray.java:1613:in `each'", "(eval):719:in`initialize'", "org/jruby/RubyProc.java:281:in `call'", "(eval):744:in`initialize'", "org/jruby/RubyArray.java:1613:in `each'", "(eval):738:in`initialize'", "org/jruby/RubyProc.java:281:in `call'", "(eval):472:in`filter\_func'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:398:in `filter_batch'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:379:in`worker\_loop'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:342:in `start_workers'"]} [2017-10-17T16:55:36,312][FATAL][logstash.runner] An unexpected error occurred! {:error=>#<NoMethodError: undefined method`\<' for nil:NilClass\>, :backtrace=\>["(eval):704:in `initialize'", "org/jruby/RubyArray.java:1613:in`each'", "(eval):702:in `initialize'", "org/jruby/RubyProc.java:281:in`call'", "(eval):722:in `initialize'", "org/jruby/RubyArray.java:1613:in`each'", "(eval):719:in `initialize'", "org/jruby/RubyProc.java:281:in`call'", "(eval):744:in `initialize'", "org/jruby/RubyArray.java:1613:in`each'", "(eval):738:in `initialize'", "org/jruby/RubyProc.java:281:in`call'", "(eval):472:in `filter_func'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:398:in`filter\_batch'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:379:in `worker_loop'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:342:in`start\_workers'"]}

---

<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:** [November 15, 2017, 10:17am UTC](https://discuss.elastic.co/t/logstash-start-killed/104225/3 "2017-11-15T10:17:56Z")

</div>

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