Databases
StackOverflow2013
Postsdbo
POElasticSearch disappearing / crashing -- cannot find log files or any other information
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POElasticSearch disappearing / crashing -- cannot find log files or any other information
    text
    copied!<p>I'm running ElasticSearch on my EC2 servers. I'm having trouble understanding the logging / debugging of ElasticSearch.</p> <p>Occasionally, the service disappears, after having been running fine for days (I expect that it's crashing). Eg:</p> <pre><code># curl -XGET http://localhost:9200/ curl: (7) couldn't connect to host </code></pre> <p>Per <a href="http://www.elasticsearch.org/guide/reference/setup/configuration.html" rel="noreferrer">this ElasticSearch page</a>, I expected that my logs would be available in <code>/var/log/elasticsearch</code>... however...</p> <pre><code># ls /var/data/elasticsearch ls: /var/data/elasticsearch: No such file or directory </code></pre> <p>I have not changed the <code>/config/logging.yml</code> file in any way. ElasticSearch is running as root, so there should be no problem with permissions.</p> <p>What am I missing?</p> <hr> <p>Per imotov's response, I found my log files at <code>/root/elasticsearch/elasticsearch-0.20.5/logs</code>... but as he predicted, they were very unhelpful. </p> <p>I checked my Java version:</p> <pre><code>java version "1.6.0_14" Java(TM) SE Runtime Environment (build 1.6.0_14-b08) Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode) </code></pre> <p>It looks like this is a very old version, and I'm working on upgrading it.</p> <p>I also had a look at my memory graph</p> <p><img src="https://i.stack.imgur.com/YldiI.png" alt="enter image description here"></p> <p>We can see that there was a weird spike just before ES died. I'm trying to discover the source, here. The only other process should be node; they're capped at 4Gb and 1.2Gb, respectively (once ES died and just node was left, the RAM dropped to 1.2Gb as you can see). So either ElasticSearch exceeded it's 4Gb, or something else caused a spike in memory...</p> <p>FWIW, I'm using m1.large instances (8GB RAM).</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload