# Pipelines.yml RemoteConfigError - Where should pipeline configs reside?

**URL:** <https://discuss.elastic.co/t/pipelines-yml-remoteconfigerror-where-should-pipeline-configs-reside/161298>\
**Category:** Logstash\
**Created:** [December 18, 2018, 9:55am UTC](https://discuss.elastic.co/t/pipelines-yml-remoteconfigerror-where-should-pipeline-configs-reside/161298 "2018-12-18T09:55:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cawoodm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cawoodm/32/14083_2.png) [@cawoodm](https://discuss.elastic.co/u/cawoodm)\
**Post date:** [December 18, 2018, 9:55am UTC](https://discuss.elastic.co/t/pipelines-yml-remoteconfigerror-where-should-pipeline-configs-reside/161298/1 "2018-12-18T09:55:28Z")

</div>

We're trying to use the multiple pipelines feature described [here](https://www.elastic.co/guide/en/logstash/current/multiple-pipelines.html) in Logstash/ES 6.5 on Windows but LogStash can apparently not see/find/read the .conf files.

We're starting logstash.bat with no parameters and our `pipelines.yml` looks like this:

```
# Pipeline for FileBeats: Application console and access logs
- pipeline.id: filebeat
  path.config: "/elk/logstash/config/pipeline.filebeat.conf"

# Pipeline for other application logs
- pipeline.id: other.logs
  path.config: "pipeline.other.logs.conf"

```

The error is:

> [2018-12-18T10:43:43,542][ERROR][logstash.config.sourceloader] Could not fetch all the sources {:exception=\>LogStash::ConfigManagement::ElasticsearchSource::RemoteConfigError, :message=\>"Empty configuration for pipeline\_id: filebeat", :backtrace=\>["D:/elk/logstash/vendor/bundle/jruby/2.3.0/gems/x-pack-6.2.2-java/lib/config\_management/elasticsearch\_source.rb:101:  
> in `get\_pipeline'", "D:/elk/logstash/vendor/bundle/jruby/2.3.0/gems/x-pack-6.2.2-java/lib/config\_management/elasticsearch\_source.rb:87:  
> ...

We have tried every variation of `path.config: "pipeline.filebeat.conf"` or `path.config: "config\pipeline.filebeat.conf"` etc.

It seems LogStash cannot find these .conf files but they do indeed exist in the `config` folder.

Adding `--debug` has not helped in seeing where LogStash expects these files.

BONUS QUESTION: How do the pipelines defined in pipeline.yml relate to those defined in `logstash.yml` in `xpack.management.pipeline.id` and those created in Kibana??

---

<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:** [January 15, 2019, 9:55am UTC](https://discuss.elastic.co/t/pipelines-yml-remoteconfigerror-where-should-pipeline-configs-reside/161298/2 "2019-01-15T09:55:37Z")

</div>

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