# Logstash aborting due to Pipeline Configuration Error **URL:** \ **Category:** Logstash\ **Created:** [July 31, 2018, 11:26am UTC](https://discuss.elastic.co/t/logstash-aborting-due-to-pipeline-configuration-error/142347 "2018-07-31T11:26:24Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![rshetty](https://avatars.discourse-cdn.com/v4/letter/r/6a8cbe/32.png) [@rshetty](https://discuss.elastic.co/u/rshetty)\ **Post date:** [July 31, 2018, 11:26am UTC](https://discuss.elastic.co/t/logstash-aborting-due-to-pipeline-configuration-error/142347/1 "2018-07-31T11:26:24Z")
I have multiple pipelines running in my logstash server that have been configured via kibana. However, I'm facing an issue where if one of the pipeline configurations has some error than the entire logstash instance aborts and the logstash service stops. How do I ensure that the logstash instance does not go down and the remaining (error-free) pipelines keep running even if any of the other pipeline's encounter an error? ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [August 1, 2018, 12:38pm UTC](https://discuss.elastic.co/t/logstash-aborting-due-to-pipeline-configuration-error/142347/2 "2018-08-01T12:38:32Z")
How are you deploying the configuration files? Before putting new files in place you can start Logstash with the config test flag to have it validate the configuration. If that test passes you can proceed with the file installation. ---
**Author:** ![rshetty](https://avatars.discourse-cdn.com/v4/letter/r/6a8cbe/32.png) [@rshetty](https://discuss.elastic.co/u/rshetty)\ **Post date:** [August 2, 2018, 8:08am UTC](https://discuss.elastic.co/t/logstash-aborting-due-to-pipeline-configuration-error/142347/3 "2018-08-02T08:08:36Z")
Hi Magnus, We are configuring the pipeline through Kibana -\> Management -\> Pipelines and specifying the pipeline ID in logstash.yml. The config test flag that you speak of is used through command line when we are loading the pipeline file through command line right? Is there anything similar that could be enabled in the logstash.yml file or any other logstash setting files? ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [August 2, 2018, 9:14am UTC](https://discuss.elastic.co/t/logstash-aborting-due-to-pipeline-configuration-error/142347/4 "2018-08-02T09:14:48Z")
> The config test flag that you speak of is used through command line when we are loading the pipeline file through command line right? Yes. > Is there anything similar that could be enabled in the logstash.yml file or any other logstash setting files? Not as far as I know. ---
**Author:** ![rshetty](https://avatars.discourse-cdn.com/v4/letter/r/6a8cbe/32.png) [@rshetty](https://discuss.elastic.co/u/rshetty)\ **Post date:** [August 2, 2018, 10:11am UTC](https://discuss.elastic.co/t/logstash-aborting-due-to-pipeline-configuration-error/142347/5 "2018-08-02T10:11:13Z")
The config test flag can be set in the logstash.yml through the setting **config.test\_and\_exit:true**. But I am encountering an error while trying to implement this. I will try to explore further and check if this solution can be used for my issue. However, I'm quite confused why does logstash abort due to a single pipeline configuration error. This blocks the execution of the remaining pipelines that are properly configured. ---
**Author:** ![rshetty](https://avatars.discourse-cdn.com/v4/letter/r/6a8cbe/32.png) [@rshetty](https://discuss.elastic.co/u/rshetty)\ **Post date:** [August 3, 2018, 11:05am UTC](https://discuss.elastic.co/t/logstash-aborting-due-to-pipeline-configuration-error/142347/6 "2018-08-03T11:05:05Z")
I am unable to set the config.test\_and\_exit:true as we have centralized pipeline management enabled. Thus it returns the error message: [logstash.modules.scaffold] Initializing module {:module\_name=\>"arcsight", :directory=\>"/opt/appl/logstash/vendor/bundle/jruby/2.3.0/gems/x-pack-6.2.3-java/modules/arcsight/configuration"} ERROR: You cannot use -t since Elasticsearch is configured as the config store IG\_STR [-t] [--log.level fatal|error|warn|info|debug|trace] [-w COUNT] [-l LOG] bin/logstash -i SHELL [--log.level fatal|error|warn|info|debug|trace] bin/logstash -V [--log.level fatal|error|warn|info|debug|trace] bin/logstash --help I was wondering if there is any alternative to configure this setting? ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [August 3, 2018, 11:06am UTC](https://discuss.elastic.co/t/logstash-aborting-due-to-pipeline-configuration-error/142347/7 "2018-08-03T11:06:37Z")
None that I know of. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 31, 2018, 11:18am UTC](https://discuss.elastic.co/t/logstash-aborting-due-to-pipeline-configuration-error/142347/8 "2018-08-31T11:18:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.