# Logstash problem with Elasticsearch

**URL:** <https://discuss.elastic.co/t/logstash-problem-with-elasticsearch/111795>\
**Category:** Logstash\
**Created:** [December 14, 2017, 3:03pm UTC](https://discuss.elastic.co/t/logstash-problem-with-elasticsearch/111795 "2017-12-14T15:03:42Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![insuk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/insuk/32/29396_2.png) [@insuk](https://discuss.elastic.co/u/insuk)\
**Post date:** [March 8, 2019, 4:03am UTC](https://discuss.elastic.co/t/logstash-problem-with-elasticsearch/111795/7 "2019-03-08T04:03:58Z")

</div>

> [@Judin](#):
>
> "ERROR: There are config files (1) in the '/etc/logstash/conf.d/winlogbeat.conf' folder. Elasticsearch is configured as the config store so configs cannot be sourced via the command line with -f or via logstash.yml with path.config"

It seems you've enabled [Centralized Pipeline Management](https://www.elastic.co/guide/en/logstash/6.6/configuring-centralized-pipelines.html#configuring-centralized-pipelines), so you can no longer specify local pipeline configurations.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-problem-with-elasticsearch/111795)._