# Ignoring the 'pipelines.yml' file because modules or command line options are specified 문의

**URL:** <https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified/155116>\
**Category:** 한국어 질문 및 토론\
**Created:** [November 2, 2018, 6:05am UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified/155116 "2018-11-02T06:05:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Minkyu\_Park](https://avatars.discourse-cdn.com/v4/letter/m/4af34b/32.png) [@Minkyu\_Park](https://discuss.elastic.co/u/Minkyu_Park)\
**Post date:** [November 2, 2018, 6:05am UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified/155116/1 "2018-11-02T06:05:19Z")

</div>

안녕하세요. 윈도우10기반의 환경의 엘라스틱 스택 6.4.2 버전에서, 엘라스틱 스택 책을 따라서, 로그스태시 설치후 책에 나온 예제를 실행시킬려고 하는데

계속해서 Ignoring the 'pipelines.yml' file because modules or command line options are specified 와 같은 오류가 나며 출력이 안되는데 이부분을 해결하고 싶습니다.

기본적인 input {stdin{}} output{stdout{}} 도 실행은 되지만 위와같은 오류가 계속해서 납니다.

logstash의 logstash.yml, pipelines.yml 은 초기에 압축풀었을때의 default와 동일하며

제가 돌렸던 .conf 구문과 정확한 오류 메세지 첨부합니다.

> # simple.conf

# 환경 설정 예제

input {  
stdin { }  
}  
filter {  
mutate {  
uppercase =\> ["message"]  
}  
output {  
stdout {  
codec =\> rubydebug  
}  
}

> C:\logstash-6.4.2\bin\>logstash -f ..\config\ch05\simple.conf  
> Sending Logstash logs to C:/logstash-6.4.2/logs which is now configured via log4j2.properties  
> [2018-11-02T14:53:19,478][WARN][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified  
> [2018-11-02T14:53:19,994][INFO][logstash.runner] Starting Logstash {"logstash.version"=\>"6.4.2"}  
> [2018-11-02T14:53:20,556][ERROR][logstash.agent] Failed to execute action {:action=\>LogStash::PipelineAction::Create/pipeline\_id:main, :exception=\>"LogStash::ConfigurationError", :message=\>"Expected one of #, =\> at line 11, column 10 (byte 119) after filter {\n mutate {\n uppercase =\> ["message"]\n}\noutput {\n stdout ", :backtrace=\>["C:/logstash-6.4.2/logstash-core/lib/logstash/compiler.rb:41:in `compile_imperative'", "C:/logstash-6.4.2/logstash-core/lib/logstash/compiler.rb:49:in `compile\_graph'", "C:/logstash-6.4.2/logstash-core/lib/logstash/compiler.rb:11:in `block in compile_sources'", "org/jruby/RubyArray.java:2486:in `map'", "C:/logstash-6.4.2/logstash-core/lib/logstash/compiler.rb:10:in `compile_sources'", "org/logstash/execution/AbstractPipelineExt.java:149:in `initialize'", "C:/logstash-6.4.2/logstash-core/lib/logstash/pipeline.rb:22:in `initialize'", "C:/logstash-6.4.2/logstash-core/lib/logstash/pipeline.rb:90:in `initialize'", "C:/logstash-6.4.2/logstash-core/lib/logstash/pipeline\_action/create.rb:38:in `execute'", "C:/logstash-6.4.2/logstash-core/lib/logstash/agent.rb:309:in `block in converge\_state'"]}  
> [2018-11-02T14:53:20,978][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=\>9600}

---

<div class="post-metadata">

**Author:** ![kimjmin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimjmin/32/15223_2.png) [@kimjmin](https://discuss.elastic.co/u/kimjmin)\
**Post date:** [November 23, 2018, 5:40am UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified/155116/2 "2018-11-23T05:40:51Z")

</div>

> Ignoring the 'pipelines.yml' file...

위 내용은 오류가 아니고 -f 또는 -e 옵션으로 실행하셨기 때문에 pipeline.yml 파일 내용은 무시한다는 메시지입니다.

---

<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:** [December 21, 2018, 5:40am UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified/155116/3 "2018-12-21T05:40:54Z")

</div>

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