# Multipipeline Issues **URL:** \ **Category:** Logstash\ **Created:** [January 28, 2018, 5:46am UTC](https://discuss.elastic.co/t/multipipeline-issues/117347 "2018-01-28T05:46:07Z")\ **Posts on this page:** 1\ **Showing post:** 15
**Author:** ![harshbajaj16](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/harshbajaj16/32/44970_2.png) [@harshbajaj16](https://discuss.elastic.co/u/harshbajaj16)\ **Post date:** [February 23, 2018, 4:36am UTC](https://discuss.elastic.co/t/multipipeline-issues/117347/15 "2018-02-23T04:36:20Z")
yes i was talking about linux. bcoz earlier we faced same issue and got resolved by this. and also provide this solution to others and it works so i thought u might have same issue. > [@Migration issues from Logstash 2.4 to 5.6](https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888/4): > > path.settings: /etc/logstash/conf.d it seems there is space b/w ': /etc/' pls check the same in your conf file and remove it. OR 5.0 forces you to have the settings file. But the default settings file has a row: path.config: /etc/logstash/conf.d This becomes a problem if you run the application and use -f to point it to a custom configuration file like this. sudo /usr/share/logstash/bin/logstash -f /home/ec2-user/logstashfileinput.yaml --path.settings /etc/logstash/ Whatever file you poi… --- _[View the full topic](https://discuss.elastic.co/t/multipipeline-issues/117347)._