Logstash with X-PACK Cannot reload pipeline, because the existing pipeline is not reloadable

Enviroment:
Logstash version: 6.2.4
Elasticsearch version: 6.2.4
kibana: 6.2.4

logstash.yml:

> config.reload.automatic: true
> config.reload.interval: 3s
> pipeline.id: elk_logstash_01
> pipeline. reloadable: true
> xpack.management.enabled: true
> xpack.management.elasticsearch.url: "http://192.168.0.9:8200/"
> xpack.management.elasticsearch.username: elastic
> xpack.management.elasticsearch.password: elastic
> xpack.management.logstash.poll_interval: 5s
> xpack.management.pipeline.id: ["elk_logstash_01"]

When I change the pipeline in kibana, the logstash can not reload the relevant pipeline, and log error:

[2018-05-23T13:37:54,661][ERROR][logstash.agent           ] Failed to execute action {:id=>:elk_logstash_01, :action_type=>LogStash::ConvergeResult::FailedAction, :message=>"Cannot reload pipeline, because the existing pipeline is not reloadable", :backtrace=>nil}

Perhaps you're using an input/output/filter/codec plugin that doesn't support reloading?

Pipeline used for me is:

input { stdin { } }

filter {
   csv {
     separator => "*"
     columns => ["f1", "f2", "f3"]
   }
}

output {
  elasticsearch {
       hosts => ["192.168.0.9:8200"]
       user => logstash_internal
       password => logstash_internal
  }
  stdout { codec => rubydebug }
}

becasuse the stdin and stdout?

stdoutis fine but I would not expect stdin to work.

I resolve this problem by removal the both stdin and stdoutfinally. Thanks @Christian_Dahlqvist @magnusbaeck

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