# Migration issues from Logstash 2.4 to 5.6 **URL:** \ **Category:** Logstash\ **Created:** [February 14, 2018, 11:27pm UTC](https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888 "2018-02-14T23:27:52Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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 20, 2018, 3:25am UTC](https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888/4 "2018-02-20T03:25:25Z")
> [@motts](#): > > path.settings: /etc/logstash/conf.d 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 point to using -f gets ignored and instead uses the file located at /etc/logstash/conf.d/. Assuming there even is one. The settings file takes precedence over whatever you pass in as a command line flag. If you were already planning on using that file then it isn't a problem, but for my cases I wasn't. I haven't tested it, but it's possible that whatever is in the settings file would also take precedence over -w and -b too. --- _[View the full topic](https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888)._