# Error when using multi pipeline config

**URL:** <https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207>\
**Category:** Logstash\
**Created:** [March 16, 2018, 5:32am UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207 "2018-03-16T05:32:07Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![br14nb0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/br14nb0/32/28814_2.png) [@br14nb0](https://discuss.elastic.co/u/br14nb0)\
**Post date:** [March 16, 2018, 5:32am UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207/1 "2018-03-16T05:32:07Z")

</div>

I have this error when I try to run multi pipeline config  
"ERROR: Failed to read pipelines yaml file. Location: C:/elk/logstash/config/pipelines.yml"  
And this is the content of my pipelines.yml

- pipeline.id: sharepoint  
pipeline.workers: 1  
pipeline.batch.size: 1  
path.config: "C:\elk\logstash\bin\config\_sharepoint.json"
- pipeline.id: beats  
pipeline.workers: 1  
pipeline.batch.size: 1  
path.config: "C:\elk\logstash\bin\config.json"

---

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [March 17, 2018, 6:58am UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207/2 "2018-03-17T06:58:15Z")

</div>

Are there any other lines indicating permissions issues? I am not an expert on Windows filesystem permissions, but generally when a file can't be read, checking permissions is a good place to start.

How are you launching Logstash? Is it getting launched as its own service user (and if so, does _that_ user have permission to read the file)? Are there any other log lines that could be relevant?

---

<div class="post-metadata">

**Author:** ![br14nb0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/br14nb0/32/28814_2.png) [@br14nb0](https://discuss.elastic.co/u/br14nb0)\
**Post date:** [March 17, 2018, 7:14am UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207/3 "2018-03-17T07:14:10Z")

</div>

When I launch logstash as a service, it return "Skipping following files ... since not match specified glob pattern" including my first file config that showed in pipeline.yml with pipeline.id: sharepoint. It means the first one config file is not read but the second one is good. Therefore, I try to run logstash by command line as admin then Error is appeared

---

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [March 17, 2018, 7:25am UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207/4 "2018-03-17T07:25:22Z")

</div>

> [@br14nb0](#):
>
> I try to run logstash by command line as admin

What command did you run?

Tip: if you fence your code with a `~~~` line before and after, it makes it easier to read 🙂

---

<div class="post-metadata">

**Author:** ![br14nb0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/br14nb0/32/28814_2.png) [@br14nb0](https://discuss.elastic.co/u/br14nb0)\
**Post date:** [March 17, 2018, 8:07am UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207/5 "2018-03-17T08:07:42Z")

</div>

Just .\logstash

And when I skipped the multi pipeline, I used multi config with "-f".  
.\logstash -f "C:\elk\logstash\config"  
Error as well

---

<div class="post-metadata">

**Author:** ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)\
**Post date:** [March 17, 2018, 4:59pm UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207/6 "2018-03-17T16:59:09Z")

</div>

Multipipeline doesn't like drive letters in the path, not sure what that means for boxes with multiple drives but try the below, it should work and yes, use forward slashes.

`path.config: "/elk/logstash/bin/config_sharepoint.json"`

---

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [March 17, 2018, 5:32pm UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207/7 "2018-03-17T17:32:25Z")

</div>

> [@wwalker](#):
>
> Multipipeline doesn't like drive letters in the path

That sounds like a bug; would you mind filing a ticket on the [GitHub project](https://github.com/elastic/logstash) since you know more about it than me?

---

<div class="post-metadata">

**Author:** ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)\
**Post date:** [March 17, 2018, 5:35pm UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207/8 "2018-03-17T17:35:59Z")

</div>

> [@yaauie](#):
>
> > [@wwalker](#):
> >
> > Multipipeline doesn't like drive letters in the path
> 
> That sounds like a bug; would you mind filing a ticket on the [GitHub project](https://github.com/elastic/logstash) since you know more about it than me?

Indeed it does, although a search of issues on GitHub shows an [existing ticket open](https://github.com/elastic/logstash/issues/6311) from about a year and a half ago regarding drive letters being capitalized which may still be the case. OP, would you mind trying without a capitalized drive letter, see if it works then?

---

<div class="post-metadata">

**Author:** ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)\
**Post date:** [March 19, 2018, 3:40am UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207/9 "2018-03-19T03:40:00Z")

</div>

> [@wwalker](#):
>
> > [@yaauie](#):
> >
> > > [@wwalker](#):
> > >
> > > Multipipeline doesn't like drive letters in the path
> > 
> > That sounds like a bug; would you mind filing a ticket on the [GitHub project](https://github.com/elastic/logstash) since you know more about it than me?
> 
> Indeed it does, although a search of issues on GitHub shows an [existing ticket open](https://github.com/elastic/logstash/issues/6311) from about a year and a half ago regarding drive letters being capitalized which may still be the case. OP, would you mind trying without a capitalized drive letter, see if it works then?

Looks like this is a separate issue. I was just going through some testing on something else and tried this out, still does not like it with a drive letter, even when it's not capitalized. I've submitted a ticket to GitHub, detailing the findings.

---

<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:** [April 16, 2018, 3:40am UTC](https://discuss.elastic.co/t/error-when-using-multi-pipeline-config/124207/10 "2018-04-16T03:40:23Z")

</div>

Closed on April 16, 2018, 3:40am UTC

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