# Ignoring the 'pipelines.yml' file because modules or command line options are specified - RPM **URL:** \ **Category:** Logstash\ **Created:** [May 31, 2019, 10:30pm UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified-rpm/183795 "2019-05-31T22:30:58Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Bhargav\_Ram\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhargav_ram_reddy/32/47118_2.png) [@Bhargav\_Ram\_Reddy](https://discuss.elastic.co/u/Bhargav_Ram_Reddy)\ **Post date:** [May 31, 2019, 10:30pm UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified-rpm/183795/1 "2019-05-31T22:30:58Z")
i have installed logstash through RPM on my ec2 instance and started \< ./logstash --path.settings /etc/logstash/ --path.config /etc/logstash/ /\> but i see below error. Can someone help out here? > [root@ip-10-1-1-133 bin]# ./logstash --path.settings /etc/logstash/ --path.config /etc/logstash/ -e > OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N > Sending Logstash logs to /var/log/logstash which is now configured via log4j2.properties > [2019-05-31T22:24:41,524][WARN][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified > [2019-05-31T22:24:41,557][INFO][logstash.runner] Starting Logstash {"logstash.version"=\>"7.1.1"} > [2019-05-31T22:24:43,632][ERROR][logstash.agent] Failed to execute action {:action=\>LogStash::PipelineAction::Create/pipeline\_id:main, :exception=\>"LogStash::ConfigurationError", :message=\>"Expected one of #, input, filter, output at line 6, column 1 (byte 132) after ## JVM configuration\n\n# Xms represents the initial size of total heap space\n# Xmx represents the maximum size of total heap space\n\n", :backtrace=\>["/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:41:in `compile_imperative'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:49:in `compile\_graph'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:11:in `block in compile_sources'", "org/jruby/RubyArray.java:2577:in `map'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:10:in `compile_sources'", "org/logstash/execution/AbstractPipelineExt.java:151:in `initialize'", "org/logstash/execution/JavaBasePipelineExt.java:47:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:23:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline\_action/create.rb:36:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:325:in `block in converge\_state'"]} > [2019-05-31T22:24:44,213][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=\>9600} > [2019-05-31T22:24:48,975][INFO][logstash.runner] Logstash shut down. pipelines.yml in /etc/logstash directory > -pipeline.id: access\_logs > path.config: "/etc/logstash/pipelines/access.conf" > -pipeline.id: error\_logs > path.config: "/etc/logstash/pipelines/errors.conf" ---
**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:** [May 31, 2019, 10:46pm UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified-rpm/183795/2 "2019-05-31T22:46:04Z")
You have specified --path.config on the command line, so it will ignore pipelines.yml. Instead it loads every file it can find in the directory you specified, which include jvm.options -- that is what results in that error message. ---
**Author:** ![Bhargav\_Ram\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhargav_ram_reddy/32/47118_2.png) [@Bhargav\_Ram\_Reddy](https://discuss.elastic.co/u/Bhargav_Ram_Reddy)\ **Post date:** [May 31, 2019, 10:50pm UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified-rpm/183795/3 "2019-05-31T22:50:31Z")
what's solution here ? same error when i do this > ./logstash --path.settings /etc/logstash/ --path.config /etc/logstash/pipelines.yml ---
**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:** [May 31, 2019, 10:54pm UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified-rpm/183795/4 "2019-05-31T22:54:25Z")
Remove --path.config from the command line. ---
**Author:** ![Bhargav\_Ram\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhargav_ram_reddy/32/47118_2.png) [@Bhargav\_Ram\_Reddy](https://discuss.elastic.co/u/Bhargav_Ram_Reddy)\ **Post date:** [May 31, 2019, 10:59pm UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified-rpm/183795/5 "2019-05-31T22:59:15Z")
then i face this issue > ERROR: Failed to read pipelines yaml file. Location: /etc/logstash/pipelines.yml Do you think there is something wrong with the pipelines.yml content ? ---
**Author:** ![Bhargav\_Ram\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhargav_ram_reddy/32/47118_2.png) [@Bhargav\_Ram\_Reddy](https://discuss.elastic.co/u/Bhargav_Ram_Reddy)\ **Post date:** [May 31, 2019, 11:02pm UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified-rpm/183795/6 "2019-05-31T23:02:37Z")
ah the issue is with pipelines.yml content ther should be space after '-' ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 28, 2019, 11:02pm UTC](https://discuss.elastic.co/t/ignoring-the-pipelines-yml-file-because-modules-or-command-line-options-are-specified-rpm/183795/7 "2019-06-28T23:02:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.