# Elasticsearch crashes before it starts **URL:** \ **Category:** Elasticsearch\ **Created:** [May 8, 2019, 8:53pm UTC](https://discuss.elastic.co/t/elasticsearch-crashes-before-it-starts/180252 "2019-05-08T20:53:39Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Sophivorus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sophivorus/32/45847_2.png) [@Sophivorus](https://discuss.elastic.co/u/Sophivorus)\ **Post date:** [May 8, 2019, 8:53pm UTC](https://discuss.elastic.co/t/elasticsearch-crashes-before-it-starts/180252/1 "2019-05-08T20:53:40Z")
I'm trying to install Elasticsearch 6.5 on my DreamHost VPS running Ubuntu 14.04 (the "old" version of Elasticsearch is because I'm interested in installing a [MediaWiki extension](https://www.mediawiki.org/wiki/Extension:CirrusSearch) that requires it). I downloaded and extracted the Elasticsearch 6.5 tarball, which according to the [JVM support matrix](https://www.elastic.co/support/matrix#matrix_jvm), requires OpenJDK 11. My VPS was running an old Java version, so I downloaded OpenJDK 11 and set the following to both my .bash\_profile and .bashrc: ```auto export JDK_HOME=/path/to/jdk export JAVA_HOME=/path/to/jdk export PATH=/path/to/jdk/bin:$PATH ``` Now when I run `java -version` from my SSH console, I get version 11. So far so good. But when I run `./bin/elasticsearch` as per [the install instructions](https://www.elastic.co/guide/en/elasticsearch/reference/6.5/zip-targz.html), I get the following two lines and then my console crashes: ```auto OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. OpenJDK 64-Bit Server VM warning: UseAVX=2 is not supported on this CPU, setting it to UseAVX=1 ``` I can find no logs anywhere or any clue as to why it crashes. I suspect that maybe Elasticsearch is trying to write files somewhere my VPS is forbidding, because before I figured out what versions I needed, I tried installing Elasticsearch 7 (which comes bundled with OpenJDK and is not supported on Ubuntu 14.04) and got the same warnings and crash. Anyone has a clue on what may be going on or how to find out?? Any help is appreciated, thanks! ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 8, 2019, 9:12pm UTC](https://discuss.elastic.co/t/elasticsearch-crashes-before-it-starts/180252/2 "2019-05-08T21:12:02Z")
Please share the entire command you are running and its output, including things like your shell prompt 🙂 ---
**Author:** ![Sophivorus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sophivorus/32/45847_2.png) [@Sophivorus](https://discuss.elastic.co/u/Sophivorus)\ **Post date:** [May 8, 2019, 10:19pm UTC](https://discuss.elastic.co/t/elasticsearch-crashes-before-it-starts/180252/3 "2019-05-08T22:19:32Z")
Thanks for the quick answer. I have shared both the command I'm running: ``` ./bin/elasticsearch ``` And the output before the crash: ``` OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. OpenJDK 64-Bit Server VM warning: UseAVX=2 is not supported on this CPU, setting it to UseAVX=1 ``` I'm afraid there isn't anything else. I've been looking for logs inside and outside the elasticsearch directory, but haven't find any. ---
**Author:** ![mgaspereyra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mgaspereyra/32/32753_2.png) [@mgaspereyra](https://discuss.elastic.co/u/mgaspereyra)\ **Post date:** [May 9, 2019, 2:14am UTC](https://discuss.elastic.co/t/elasticsearch-crashes-before-it-starts/180252/4 "2019-05-09T02:14:40Z")
Hi, did you checked this? > It's almost the same issue. It seems that you're facing (possibly) read permissions. Can you modify your elastic config file to point data path to some path where the file permissions are right to your elastic user/daemon? ---
**Author:** ![Sophivorus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sophivorus/32/45847_2.png) [@Sophivorus](https://discuss.elastic.co/u/Sophivorus)\ **Post date:** [May 9, 2019, 6:44pm UTC](https://discuss.elastic.co/t/elasticsearch-crashes-before-it-starts/180252/5 "2019-05-09T18:44:25Z")
Hi, thanks for the help! I tried setting: ``` path.data: /path/to/elasticsearch/data path.logs: /path/to/elasticsearch/logs ``` in `config/elasticsearch.yml` (with `/path/to` being my real path, of course) and then reboot the server and run: ``` ./bin/elasticsearch ``` but I get the same old error with no output or logs. ☹ I tried setting the directory permissions to 777 with: ``` chmod 777 -R /path/to/elastichsearch ``` but no luck, same result. How can I know my elastic user/daemon? The issue you linked seems similar from the title, but in their case at least they got some output to work with. In my case, Elasticsearch (and my console) crashes before it even prints "Initializing..." ! Is there some "hidden" verbose or debug mode for Elasticsearch? Once again, thanks. ---
**Author:** ![mgaspereyra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mgaspereyra/32/32753_2.png) [@mgaspereyra](https://discuss.elastic.co/u/mgaspereyra)\ **Post date:** [May 10, 2019, 2:37pm UTC](https://discuss.elastic.co/t/elasticsearch-crashes-before-it-starts/180252/6 "2019-05-10T14:37:13Z")
Hi! Can you paste the "ls -l" output from your data & logs paths? That in order to check the ownership of directories. Also, according the command "./bin/elasticsearch" I'm assuming you're using a tarball distribution. It's that correct? In my particular case, I'm using that distribution, and I've created an exclusive unix user form elastic stack, so, I've granted explicit privileges for that user, because it's the one running the processes. ---
**Author:** ![Sophivorus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sophivorus/32/45847_2.png) [@Sophivorus](https://discuss.elastic.co/u/Sophivorus)\ **Post date:** [May 10, 2019, 8:41pm UTC](https://discuss.elastic.co/t/elasticsearch-crashes-before-it-starts/180252/7 "2019-05-10T20:41:01Z")
Hola Gastón, thanks for your continued help! Yes, I'm using the tarball distribution. The output of `ls -l` for my data and logs paths is: ``` drwxrwxrwx 2 wikimix pg9073652 10 May 9 11:22 data drwxrwxrwx 2 wikimix pg9073652 27 May 9 11:34 logs ``` I've done some more reading but I found no (updated) documentation on how to know what user is running my Elasticsearch processes, or how to set it. Do you know? Thanks again, ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 7, 2019, 8:41pm UTC](https://discuss.elastic.co/t/elasticsearch-crashes-before-it-starts/180252/8 "2019-06-07T20:41:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.