# Can't start Elasticsearch on Ubuntu 19.10 **URL:** \ **Category:** Elasticsearch\ **Created:** [October 20, 2019, 1:28pm UTC](https://discuss.elastic.co/t/cant-start-elasticsearch-on-ubuntu-19-10/204353 "2019-10-20T13:28:09Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![dandago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dandago/32/56215_2.png) [@dandago](https://discuss.elastic.co/u/dandago)\ **Post date:** [October 20, 2019, 1:28pm UTC](https://discuss.elastic.co/t/cant-start-elasticsearch-on-ubuntu-19-10/204353/1 "2019-10-20T13:28:09Z")
I am trying to run Elasticsearch on Ubuntu 19.10, which was released just three days ago. 1. I downloaded the Elasticsearch 7.4.0 .tar.gz file from [https://www.elastic.co/downloads/elasticsearch](https://www.elastic.co/downloads/elasticsearch) 2. I extracted the .tar.gz 3. I tried executing `./elasticsearch` 4. The output was: ```auto ubuntu@ubuntu:~/Downloads/elasticsearch-7.4.0-linux-x86_64/elasticsearch-7.4.0/bin$ ./elasticsearch Exception in thread "main" java.lang.RuntimeException: starting java failed with [137] output: error: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. at org.elasticsearch.tools.launchers.JvmErgonomics.flagsFinal(JvmErgonomics.java:111) at org.elasticsearch.tools.launchers.JvmErgonomics.finalJvmOptions(JvmErgonomics.java:79) at org.elasticsearch.tools.launchers.JvmErgonomics.choose(JvmErgonomics.java:57) at org.elasticsearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:89) ``` Obviously there is a Java exception, and while I don't have Java installed, it should presumably be using the bundled JDK. I know there are other options such as the .deb package, but I wanted to give it a try running it like this, and have no idea why it won't work. ---
**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\ **Post date:** [October 20, 2019, 1:39pm UTC](https://discuss.elastic.co/t/cant-start-elasticsearch-on-ubuntu-19-10/204353/2 "2019-10-20T13:39:06Z")
Hi @dandago See here: > Exception in thread "main" java.lang.RuntimeException: starting java failed with [137] Error `137` means that the system failed to allocate enough memory for the Java process. The default `jvm.options` provided by us will require at least 1GB of free memory available for the Elasticsearch process to run. In practice you will probably need a little more than that. ---
**Author:** ![dandago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dandago/32/56215_2.png) [@dandago](https://discuss.elastic.co/u/dandago)\ **Post date:** [October 20, 2019, 1:41pm UTC](https://discuss.elastic.co/t/cant-start-elasticsearch-on-ubuntu-19-10/204353/3 "2019-10-20T13:41:24Z")
Makes sense, I was testing it out from the live CD on a laptop with 4GB RAM. Thanks. Is there anywhere I can look up those error codes? It really would have been much nicer if the output just told me what the problem was. 🙂 ---
**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\ **Post date:** [October 20, 2019, 1:51pm UTC](https://discuss.elastic.co/t/cant-start-elasticsearch-on-ubuntu-19-10/204353/4 "2019-10-20T13:51:44Z")
@dandago I'm afraid there's no nice list out that there that would've give you a straight-forward explanation of the `137`. The way that one comes about is, that exit codes of the form `128+n` mean, "stopped by signal n", in this case 9 == SIGKILL, which unless you sent it yourself, is generally the OS killing the process for using up too much memory. There's a little more documentation on this topic here [https://www.tldp.org/LDP/abs/html/exitcodes.html](https://www.tldp.org/LDP/abs/html/exitcodes.html) if you're interested. ---
**Author:** ![creaticious](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/creaticious/32/24784_2.png) [@creaticious](https://discuss.elastic.co/u/creaticious)\ **Post date:** [October 22, 2019, 5:55am UTC](https://discuss.elastic.co/t/cant-start-elasticsearch-on-ubuntu-19-10/204353/5 "2019-10-22T05:55:08Z")
Had the same issue today...upgrading from 7.3 to 7.4 on Ubuntu 16.10. I'm running elastic with ES\_JAVA\_OPTS: "-Xms4g -Xmx4g -XX:-AssumeMP"...on a machine with 32GB RAM...so i guess it can't be a memory thing... ...switching back to 7.3 with the same options and everything is working again... ---
**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\ **Post date:** [October 22, 2019, 6:35pm UTC](https://discuss.elastic.co/t/cant-start-elasticsearch-on-ubuntu-19-10/204353/6 "2019-10-22T18:35:42Z")
@creaticious That's quite strange. When ES dies on a `137` you should get an error dump (`hs_*` file), could you share that if it gets produced? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 19, 2019, 6:35pm UTC](https://discuss.elastic.co/t/cant-start-elasticsearch-on-ubuntu-19-10/204353/7 "2019-11-19T18:35:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.