# Startup options conflict?

**URL:** <https://discuss.elastic.co/t/startup-options-conflict/86884>\
**Category:** Elasticsearch\
**Created:** [May 24, 2017, 1:52am UTC](https://discuss.elastic.co/t/startup-options-conflict/86884 "2017-05-24T01:52:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jaff](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jaff/32/18382_2.png) [@Jaff](https://discuss.elastic.co/u/Jaff)\
**Post date:** [May 24, 2017, 1:52am UTC](https://discuss.elastic.co/t/startup-options-conflict/86884/1 "2017-05-24T01:52:41Z")

</div>

We are migrating from ES-2.3 to ES-5.4.0 and I am updating chef infrastructure code to accommodate both versions. When I install 2.3 to Ubuntu hosts, we have it configured to run as a daemon, using some boilerplate config files with app-specific settings.  
I've noticed that when I install 5.4.0, it writes a jvm.options file that may be conflicting with some environment variables being set in our daemon-config. My question is, if I split those jvm settings out of our config and use the /config/jvm.options, is it picked up automatically? As it is, I am not able to get the app started at this time, but not getting anything logged to point out what's causing the thrashing.

---

<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:** [June 21, 2017, 1:52am UTC](https://discuss.elastic.co/t/startup-options-conflict/86884/2 "2017-06-21T01:52:50Z")

</div>

Closed on June 21, 2017, 1:52am UTC

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