# Config paths not being respected

**URL:** <https://discuss.elastic.co/t/config-paths-not-being-respected/200908>\
**Category:** Elasticsearch\
**Created:** [September 24, 2019, 4:59pm UTC](https://discuss.elastic.co/t/config-paths-not-being-respected/200908 "2019-09-24T16:59:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mdavis](https://avatars.discourse-cdn.com/v4/letter/m/49beb7/32.png) [@mdavis](https://discuss.elastic.co/u/mdavis)\
**Post date:** [September 24, 2019, 4:59pm UTC](https://discuss.elastic.co/t/config-paths-not-being-respected/200908/1 "2019-09-24T16:59:31Z")

</div>

I have a one node server setup, it works fine when the files are in the default location. I update /etc/elasticsearch/elasticsearch.yml to the new path and restart after moving the entire directory. Then the service fails to come up, and the error log either says cannot find path.data = /var/lib/elasticsearch.  
If I change the config then it still fails but says "default.path.data" cannot be found.

What am I missing?

---

<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:** [October 22, 2019, 4:59pm UTC](https://discuss.elastic.co/t/config-paths-not-being-respected/200908/2 "2019-10-22T16:59:33Z")

</div>

Closed on October 22, 2019, 4:59pm UTC

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