# Migration issues from Logstash 2.4 to 5.6

**URL:** <https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888>\
**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:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![motts](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@motts](https://discuss.elastic.co/u/motts)\
**Post date:** [February 14, 2018, 11:27pm UTC](https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888/1 "2018-02-14T23:27:53Z")

</div>

Hello there,

I am trying to migrate from 2.4 to 5.6 on CentOS 6.9 and I have a slight issue. When I try to start logstash via

`/etc/init.d/logstash.rpmsave start logstash`

I get an error in logstash.err stating

```
WARNING: Could not find logstash.yml which is typically located in $LS_HOME/config or /etc/logstash. You can specify the path using --path.settings. Continuing using the defaults
ERROR: No configuration file was specified. Perhaps you forgot to provide the '-f yourlogstash.conf' flag?

```

it appears the warning is normal, but I cannot seem to find a solution to the error listed. I have my logstash.yml file stating the path for the config file

`path.config: /etc/logstash/conf.d`

Am I on the right track or am I missing something here? Also, is there a way to get it back to where I can type `service logstash start` or is this the way of starting logstash now?

Thank you

---

<div class="post-metadata">

**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 19, 2018, 11:25am UTC](https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888/2 "2018-02-19T11:25:17Z")

</div>

it seems your conf file path is not set in path setting file or you can run with conf file with start command.

---

<div class="post-metadata">

**Author:** ![motts](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@motts](https://discuss.elastic.co/u/motts)\
**Post date:** [February 19, 2018, 1:51pm UTC](https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888/3 "2018-02-19T13:51:14Z")

</div>

the conf file path is set in my logstash.yml file as follows:

`path.settings: /etc/logstash/conf.d` that is where all the inputs, filters, and outputs are. Is this not right?

---

<div class="post-metadata">

**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")

</div>

> [@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.

---

<div class="post-metadata">

**Author:** ![motts](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@motts](https://discuss.elastic.co/u/motts)\
**Post date:** [February 20, 2018, 2:06pm UTC](https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888/5 "2018-02-20T14:06:52Z")

</div>

Awesome! Good info there. I appreciate that very much. Logstash is running smoothly now.

---

<div class="post-metadata">

**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:** [March 16, 2018, 4:36am UTC](https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888/6 "2018-03-16T04:36:53Z")

</div>

👍

---

<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:** [April 13, 2018, 4:37am UTC](https://discuss.elastic.co/t/migration-issues-from-logstash-2-4-to-5-6/119888/7 "2018-04-13T04:37:09Z")

</div>

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