# Centralised Pipeline Management reload error

**URL:** <https://discuss.elastic.co/t/centralised-pipeline-management-reload-error/156842>\
**Category:** Logstash\
**Created:** [November 15, 2018, 11:37am UTC](https://discuss.elastic.co/t/centralised-pipeline-management-reload-error/156842 "2018-11-15T11:37:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![programagor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/programagor/32/40183_2.png) [@programagor](https://discuss.elastic.co/u/programagor)\
**Post date:** [November 15, 2018, 11:37am UTC](https://discuss.elastic.co/t/centralised-pipeline-management-reload-error/156842/1 "2018-11-15T11:37:59Z")

</div>

Greetings

I just upgraded my ELK stack to 6.5.0, and 4 out of my 6 logstash nodes fail to load 1 out of 5 pipelines. The config is the same, and the pipeline is centrally managed, so I don't see why only some nodes are affected.  
Here are the relevant log entries produced when I try to manually reload the pipeline:

```auto
[2018-11-15T12:28:43,053][INFO][logstash.pipelineaction.reload] Reloading pipeline {"pipeline.id"=>:clog_dovecot}
[2018-11-15T12:28:43,061][ERROR][logstash.agent] Failed to execute action {:action=>LogStash::PipelineAction::Reload/pipeline_id:clog_dovecot, :exception=>"NoMethodError", :message=>"undefined method `call' for nil:NilClass", :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-redis-3.4.0/lib/logstash/inputs/redis.rb:110:in `stop'", "/usr/share/logstash/logstash-core/lib/logstash/inputs/base.rb:87:in `do_stop'", "org/jruby/RubyArray.java:1734:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:464:in `stop_inputs'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:447:in `shutdown'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/stop.rb:14:in `block in execute'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/stop.rb:13:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/reload.rb:53:in `block in execute'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/reload.rb:52:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:317:in `block in converge_state'"]}
[2018-11-15T12:28:48,205][INFO][logstash.pipelineaction.reload] Reloading pipeline {"pipeline.id"=>:clog_dovecot}
[2018-11-15T12:28:48,211][ERROR][logstash.agent] Failed to execute action {:action=>LogStash::PipelineAction::Reload/pipeline_id:clog_dovecot, :exception=>"NoMethodError", :message=>"undefined method `call' for nil:NilClass", :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-redis-3.4.0/lib/logstash/inputs/redis.rb:110:in `stop'", "/usr/share/logstash/logstash-core/lib/logstash/inputs/base.rb:87:in `do_stop'", "org/jruby/RubyArray.java:1734:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:464:in `stop_inputs'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:447:in `shutdown'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/stop.rb:14:in `block in execute'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/stop.rb:13:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/reload.rb:53:in `block in execute'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/reload.rb:52:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:317:in `block in converge_state'"]}

```

Restarting the affected nodes doesn't help either. How can I fix this issue?

---

<div class="post-metadata">

**Author:** ![programagor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/programagor/32/40183_2.png) [@programagor](https://discuss.elastic.co/u/programagor)\
**Post date:** [November 15, 2018, 11:55am UTC](https://discuss.elastic.co/t/centralised-pipeline-management-reload-error/156842/2 "2018-11-15T11:55:30Z")

</div>

My apologies, there was an inconsistency between files in the `/elc/logstash/patterns.d/` directory.  
Is there a way to use the centralised pipeline management to synchronise the grok patterns also?

---

<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:** [December 13, 2018, 11:55am UTC](https://discuss.elastic.co/t/centralised-pipeline-management-reload-error/156842/3 "2018-12-13T11:55:56Z")

</div>

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