# Centralized pipeline management - pipeline terminating **URL:** \ **Category:** Logstash\ **Created:** [January 20, 2018, 10:17pm UTC](https://discuss.elastic.co/t/centralized-pipeline-management-pipeline-terminating/116357 "2018-01-20T22:17:41Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![rpendela](https://avatars.discourse-cdn.com/v4/letter/r/3be4f8/32.png) [@rpendela](https://discuss.elastic.co/u/rpendela)\ **Post date:** [January 20, 2018, 10:17pm UTC](https://discuss.elastic.co/t/centralized-pipeline-management-pipeline-terminating/116357/1 "2018-01-20T22:17:41Z")
Hello community, I am trying to use the centralize pipeline management feature , I followed the document `https://www.elastic.co/guide/en/logstash/6.0/logstash-centralized-pipeline-management.html` I have a x-pack licence aswell. but after creating the pipeline using kibana UI -\> logstash -\>pipeline when I start the logstash I am getting this `Pipeline terminated {"pipeline.id"=>".monitoring-logstash"} logstash_test exited with code 0` ``` ` logstash.config.source.local.configpathloader] No config files found in path {:path=>"/usr/share/logstash/pipeline/*"}` ``` I know this error is coming because of no pipeline configuration files in the logstash pipeline directory but I guess that is not the case if I am using centralized pipeline management and if I use the same pipeline configuration in logstash/pipeline directory it is working fine. logstash not giving any errors. what might be the cause? here is my **elasticsearch.yml file** \*\*[node.name](http://node.name): elastic-test \*\* **[cluster.name](http://cluster.name): "elk-cluster"** **network.host: 0.0.0.0** **network.bind\_host: 0.0.0.0** **transport.tcp.port: 9300** **http.port: 9200** **network.publish\_host: _._._._** **discovery.zen.minimum\_master\_nodes: 1** **discovery.type: single-node** **xpack.security.enabled: false** Kibana.yml **server.host: "0"** **[server.name](http://server.name): kibana-test** **elasticsearch.url: "http://elasticsearch\_test:9200"** **elasticsearch.username: ######** **elasticsearch.password:######** **xpack.monitoring.ui.container.elasticsearch.enabled: true** **#xpack.security.enabled: true** Logstash.yml **[node.name](http://node.name): logstash-1** **http.host: "0.0.0.0"** **path.config: /usr/share/logstash/pipeline** **config.reload.automatic: true** **#xpack.monitoring.enabled: true** **#xpack.monitoring.elasticsearch.url: "http://#.#.#.#:9200"** **#xpack.monitoring.elasticsearch.username: logstash\_system** **#xpack.monitoring.elasticsearch.password: changeme** **xpack.management.enabled: true** **xpack.management.elasticsearch.url: "http://#.#.#.#:9200/"** **xpack.management.elasticsearch.username: logstash\_admin\_user** **xpack.management.elasticsearch.password: elastic** **xpack.management.logstash.poll\_interval: 5s** **[xpack.management.pipeline.id](http://xpack.management.pipeline.id): ["paloalto", "winlogbeats"]** My docker-compose file ``` `version: '2.2' ``` services: ######## ELASTICSEARCH ###################### elasticsearch: build: /usr/share/elk/elasticsearch/ container\_name: elasticsearch\_test environment: - cluster.name=elk-cluster - bootstrap.memory\_lock=true - "ES\_JAVA\_OPTS=-Xms512m -Xmx512m" - ELASTIC\_PASSWORD=changeme ulimits: nofile: soft: 65536 hard: 65536 memlock: soft: -1 hard: -1 mem\_limit: 1g ports: - 9300:9300 - 9200:9200 restart: always volumes: - es\_data1:/usr/share/elasticsearch/data - /usr/share/elk/configs/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml networks: - elk ########### LOGSTASH ########### logstash: build: /usr/share/elk/logstash/ container\_name: logstash\_test environment: - cluster.name=elk-cluster - bootstrap.memory\_lock=true - "LS\_JAVA\_OPTS=-Xms512m -Xmx512m" ulimits: nofile: soft: 65536 hard: 65536 memlock: soft: -1 hard: -1 mem\_limit: 1g ports: - 5000:5000 - 1514:1514 - 5044:5044 - 7575:7575 volumes: - ls\_data1:/usr/share/logstash/data - /usr/share/elk/configs/logstash.yml:/usr/share/config/logstash.yml - /usr/share/elk/logstash/pipeline:/usr/share/logstash/pipeline networks: - elk depends\_on: - elasticsearch ################ KIBANA ############### kibana: build: /usr/share/elk/kibana/ container\_name: kibana\_test environment: - cluster.name=elk-cluster #- "ELASTICSEARCH\_URL=http://elasticsearch:9200" mem\_limit: 1g volumes: - kibana\_data1:/usr/share/kibana/data - /usr/share/elk/configs/kibana.yml:/usr/share/kibana/config/kibana.yml ports: - "5601:5601" networks: - elk depends\_on: - elasticsearch volumes: es\_data1: driver: local ls\_data1: driver: local kibana\_data1: driver: local networks: elk: driver: bridge` ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [January 26, 2018, 9:28pm UTC](https://discuss.elastic.co/t/centralized-pipeline-management-pipeline-terminating/116357/2 "2018-01-26T21:28:22Z")
When you are using centralized configuration management, can you try commenting out the `path.config` line in your `logstash.yml` file? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 23, 2018, 9:28pm UTC](https://discuss.elastic.co/t/centralized-pipeline-management-pipeline-terminating/116357/3 "2018-02-23T21:28:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.