# Path.data does not work with my configuration in 18.2 **URL:** \ **Category:** Elasticsearch\ **Created:** [November 11, 2011, 8:45pm UTC](https://discuss.elastic.co/t/path-data-does-not-work-with-my-configuration-in-18-2/5850 "2011-11-11T20:45:51Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![phobos182](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phobos182/32/3011_2.png) [@phobos182](https://discuss.elastic.co/u/phobos182)\ **Post date:** [November 11, 2011, 8:45pm UTC](https://discuss.elastic.co/t/path-data-does-not-work-with-my-configuration-in-18-2/5850/1 "2011-11-11T20:45:51Z")
Upgraded to 18.2 from 17.7, and I'm trying to take advantage of the new comma deliminited path.data configuration. Upon startup, I receive this error. [http://pastebin.com/8CFActa7](http://pastebin.com/8CFActa7) Here is a copy of my current configuration. [http://pastebin.com/m46TCfSh](http://pastebin.com/m46TCfSh) Any advice? I have not been able to find out why path.data is not working with the local gateway settings. ---
**Author:** ![phobos182](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phobos182/32/3011_2.png) [@phobos182](https://discuss.elastic.co/u/phobos182)\ **Post date:** [November 11, 2011, 9:07pm UTC](https://discuss.elastic.co/t/path-data-does-not-work-with-my-configuration-in-18-2/5850/2 "2011-11-11T21:07:13Z")
Found out by doing a trace level debugging on "ENV" and a new ES\_PATH was getting into the daemon launch. Fixed the environment issue, and the config file was respected. Closed issue. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 13, 2011, 7:16am UTC](https://discuss.elastic.co/t/path-data-does-not-work-with-my-configuration-in-18-2/5850/3 "2011-11-13T07:16:26Z")
What exactly was the problem? I did not understand... . Also, note that there is a bug in handling multiple data locations in 0.18.2 (not distributing the data properly): [data.path locations are unevenly filled (0.18.2) · Issue #1436 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1436). On Fri, Nov 11, 2011 at 11:07 PM, phobos182 [phobos182@gmail.com](mailto:phobos182@gmail.com) wrote: > Found out by doing a trace level debugging on "ENV" and a new ES\_PATH was > getting into the daemon launch. Fixed the environment issue, and the config > file was respected. > > Closed issue. > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/path-data-does-not-work-with-my-configuration-in-18-2-tp3500902p3500947.html](http://elasticsearch-users.115913.n3.nabble.com/path-data-does-not-work-with-my-configuration-in-18-2-tp3500902p3500947.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![phobos182](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phobos182/32/3011_2.png) [@phobos182](https://discuss.elastic.co/u/phobos182)\ **Post date:** [November 14, 2011, 12:07am UTC](https://discuss.elastic.co/t/path-data-does-not-work-with-my-configuration-in-18-2/5850/4 "2011-11-14T00:07:11Z")
I back ported that patch to 18.2 from the tag. Then ran gradle, and created a new RPM package. So I'm good to go on that data path issue. BTW: The gradle build is smooth, and painless. Only took me about 10 minutes to cherry-pick the commit from git, and repackage the whole application. Good work. My issue was my init.d script. I have not checked it in a while, and it was setting a default "ES\_WORK / ES\_PATH" environment variable. This was overriding my configuration in elasticsearch.yml. Once I removed the environment variables from the init script, everything was good to go. I used debug logging on env to find out what values it was setting. Then I traced it down to my init script. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 15, 2011, 7:00am UTC](https://discuss.elastic.co/t/path-data-does-not-work-with-my-configuration-in-18-2/5850/5 "2011-11-15T07:00:51Z")
I see, thanks for the info! (wanted to double check if there si something that can be simplified in elasticsearch). On Mon, Nov 14, 2011 at 2:07 AM, phobos182 [phobos182@gmail.com](mailto:phobos182@gmail.com) wrote: > I back ported that patch to 18.2 from the tag. Then ran gradle, and > created a > new RPM package. So I'm good to go on that data path issue. BTW: The gradle > build is smooth, and painless. Only took me about 10 minutes to cherry-pick > the commit from git, and repackage the whole application. Good work. > > My issue was my init.d script. I have not checked it in a while, and it > was > setting a default "ES\_WORK / ES\_PATH" environment variable. This was > overriding my configuration in elasticsearch.yml. Once I removed the > environment variables from the init script, everything was good to go. > > I used debug logging on env to find out what values it was setting. Then I > traced it down to my init script. > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/path-data-does-not-work-with-my-configuration-in-18-2-tp3500902p3505518.html](http://elasticsearch-users.115913.n3.nabble.com/path-data-does-not-work-with-my-configuration-in-18-2-tp3500902p3505518.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:48am UTC](https://discuss.elastic.co/t/path-data-does-not-work-with-my-configuration-in-18-2/5850/6 "2017-07-06T03:48:40Z")
Closed on July 6, 2017, 3:48am UTC