# Locating Pipeline Error

**URL:** <https://discuss.elastic.co/t/locating-pipeline-error/142610>\
**Category:** Logstash\
**Created:** [August 1, 2018, 3:30pm UTC](https://discuss.elastic.co/t/locating-pipeline-error/142610 "2018-08-01T15:30:45Z")\
**Posts on this page:** 4\
**Page:** 1

<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:** [August 1, 2018, 3:30pm UTC](https://discuss.elastic.co/t/locating-pipeline-error/142610/1 "2018-08-01T15:30:46Z")

</div>

I have about 60 config files for a single pipeline and I receive the below error during Logstash startup....is there a way to pinpoint which file the error is located in?

`[2018-08-01T10:27:13,736][ERROR][logstash.agent] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:SOF, :exception=>"LogStash::ConfigurationError", :message=>"Expected one of \r, \n at line 2105, column 3 (byte 72682) after #}", :backtrace=>["D:/ElasticStack/Apps/Logstash/6.3.2/logstash-core/lib/logstash/compiler.rb:42:in`compile\_imperative'", "D:/ElasticStack/Apps/Logstash/6.3.2/logstash-core/lib/logstash/compiler.rb:50:in `compile_graph'", "D:/ElasticStack/Apps/Logstash/6.3.2/logstash-core/lib/logstash/compiler.rb:12:in`block in compile\_sources'", "org/jruby/RubyArray.java:2486:in `map'", "D:/ElasticStack/Apps/Logstash/6.3.2/logstash-core/lib/logstash/compiler.rb:11:in`compile\_sources'", "D:/ElasticStack/Apps/Logstash/6.3.2/logstash-core/lib/logstash/pipeline.rb:49:in `initialize'", "D:/ElasticStack/Apps/Logstash/6.3.2/logstash-core/lib/logstash/pipeline.rb:167:in`initialize'", "D:/ElasticStack/Apps/Logstash/6.3.2/logstash-core/lib/logstash/pipeline\_action/create.rb:40:in `execute'", "D:/ElasticStack/Apps/Logstash/6.3.2/logstash-core/lib/logstash/agent.rb:305:in`block in converge\_state'"]}`

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [August 1, 2018, 3:48pm UTC](https://discuss.elastic.co/t/locating-pipeline-error/142610/2 "2018-08-01T15:48:53Z")

</div>

Enable debug logging and --config.debug.

---

<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:** [August 17, 2018, 2:25pm UTC](https://discuss.elastic.co/t/locating-pipeline-error/142610/3 "2018-08-17T14:25:37Z")

</div>

Thanks, I could see where that could help but it spit out WAY too much and it wasn't in order so I couldn't find the line that fouled things up. When I say it wasn't in order, the console would spit out the filter section first, then half the output section, then the input and remaining output.

I ended up just pulling all the files out and putting them in one by one until it errorred out and then scanning that config for the issue.

---

<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:** [September 14, 2018, 2:25pm UTC](https://discuss.elastic.co/t/locating-pipeline-error/142610/4 "2018-09-14T14:25:40Z")

</div>

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