# Logstash 5.6.2 aborts with “warning: ignoring JAVA\_OPTS=-Xmx1024m; pass JVM parameters via LS\_JAVA\_OPTS”

**URL:** <https://discuss.elastic.co/t/logstash-5-6-2-aborts-with-warning-ignoring-java-opts-xmx1024m-pass-jvm-parameters-via-ls-java-opts/102753>\
**Category:** Logstash\
**Created:** [October 4, 2017, 7:45pm UTC](https://discuss.elastic.co/t/logstash-5-6-2-aborts-with-warning-ignoring-java-opts-xmx1024m-pass-jvm-parameters-via-ls-java-opts/102753 "2017-10-04T19:45:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![srini1](https://avatars.discourse-cdn.com/v4/letter/s/5f8ce5/32.png) [@srini1](https://discuss.elastic.co/u/srini1)\
**Post date:** [October 4, 2017, 7:45pm UTC](https://discuss.elastic.co/t/logstash-5-6-2-aborts-with-warning-ignoring-java-opts-xmx1024m-pass-jvm-parameters-via-ls-java-opts/102753/1 "2017-10-04T19:45:00Z")

</div>

I just downloaded latest versions of ELK 5.6.2 to upgrade so that I can use X-pack 5.6.2. Elasticsearch and kibana started with no issues but Logstash is aborting with the below message. "warning: ignoring JAVA\_OPTS=-Xmx1024m; pass JVM parameters via LS\_JAVA\_OPTS" I tried adding set LS\_JAVA\_OPTS="-Xms1024m -Xmx1024m" in setup.bat and also -DLS\_JAVA\_OPTS="-Xms1024m -Xmx1024m" in jvm.options file. Both doesn't seem to work . I don't see any log file being generated too. What am I doing wrong?

The command is \bin\logstatsh.bat -f logstash\_config.json I get same warning even when I check the the config with --config.test\_and\_exit and no logs. I am sure the config file is good as the same file works with logstash-5.5.1

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [October 9, 2017, 6:54pm UTC](https://discuss.elastic.co/t/logstash-5-6-2-aborts-with-warning-ignoring-java-opts-xmx1024m-pass-jvm-parameters-via-ls-java-opts/102753/2 "2017-10-09T18:54:09Z")

</div>

That's just a warning so if Logstash doesn't fire up it's probably because of something else.

> The command is \bin\logstatsh.bat -f logstash\_config.json

That's not really a JSON file, is it? Naming it logstash\_config.json doesn't strike me as a good idea, especially not as Logstash 6.0 (I believe) ignores pipeline config files whose name doesn't match \*.conf.

---

<div class="post-metadata">

**Author:** ![srini1](https://avatars.discourse-cdn.com/v4/letter/s/5f8ce5/32.png) [@srini1](https://discuss.elastic.co/u/srini1)\
**Post date:** [October 10, 2017, 3:16pm UTC](https://discuss.elastic.co/t/logstash-5-6-2-aborts-with-warning-ignoring-java-opts-xmx1024m-pass-jvm-parameters-via-ls-java-opts/102753/3 "2017-10-10T15:16:06Z")

</div>

I agree. I will change it. But why is logstatsh aborting without even printing logs? Is there much difference between 5.5.1 and 5.6.2 on how logstash starts up? 5.5.1 starts fine with the exact same config file. I don't even see a log file being generated

---

<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:** [November 7, 2017, 3:16pm UTC](https://discuss.elastic.co/t/logstash-5-6-2-aborts-with-warning-ignoring-java-opts-xmx1024m-pass-jvm-parameters-via-ls-java-opts/102753/4 "2017-11-07T15:16:08Z")

</div>

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