# Elasticsearch down after plugin installation

**URL:** <https://discuss.elastic.co/t/elasticsearch-down-after-plugin-installation/146319>\
**Category:** Elasticsearch\
**Created:** [August 28, 2018, 10:29am UTC](https://discuss.elastic.co/t/elasticsearch-down-after-plugin-installation/146319 "2018-08-28T10:29:13Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jesusgn90](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jesusgn90/32/26998_2.png) [@jesusgn90](https://discuss.elastic.co/u/jesusgn90)\
**Post date:** [August 28, 2018, 10:29am UTC](https://discuss.elastic.co/t/elasticsearch-down-after-plugin-installation/146319/1 "2018-08-28T10:29:13Z")

</div>

Hello team, since 6.4.0 I noticed that installing a plugin successfully makes Elasticsearch goes down. Then I must restart it manually and then all it's fine.

Is this an addition in 6.4.0? Why it happened?

Regards,  
Jesús

---

<div class="post-metadata">

**Author:** ![Bill\_McConaghy](https://avatars.discourse-cdn.com/v4/letter/b/ed655f/32.png) [@Bill\_McConaghy](https://discuss.elastic.co/u/Bill_McConaghy)\
**Post date:** [August 28, 2018, 11:56am UTC](https://discuss.elastic.co/t/elasticsearch-down-after-plugin-installation/146319/2 "2018-08-28T11:56:08Z")

</div>

Moved this to Elasticsearch forum as it is an ES question.

---

<div class="post-metadata">

**Author:** ![rjernst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rjernst/32/6363_2.png) [@rjernst](https://discuss.elastic.co/u/rjernst)\
**Post date:** [August 28, 2018, 4:21pm UTC](https://discuss.elastic.co/t/elasticsearch-down-after-plugin-installation/146319/3 "2018-08-28T16:21:03Z")

</div>

Installing an elasticsearch plugin should be done when elasticsearch is shut down. However, it should not cause the system to fail. Can you describe more concretely, without output from your commands, what you are seeing, including logs from elasticsearch when it stops?

---

<div class="post-metadata">

**Author:** ![jesusgn90](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jesusgn90/32/26998_2.png) [@jesusgn90](https://discuss.elastic.co/u/jesusgn90)\
**Post date:** [August 28, 2018, 4:45pm UTC](https://discuss.elastic.co/t/elasticsearch-down-after-plugin-installation/146319/4 "2018-08-28T16:45:40Z")

</div>

Sorry but what I meant is a Kibana plugin. Once the Kibana plugin installation finishes, Elasticsearch goes down with no reason . After restart Elasticsearch all is just fine...

Why?

Regards!

---

<div class="post-metadata">

**Author:** ![rjernst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rjernst/32/6363_2.png) [@rjernst](https://discuss.elastic.co/u/rjernst)\
**Post date:** [August 28, 2018, 5:58pm UTC](https://discuss.elastic.co/t/elasticsearch-down-after-plugin-installation/146319/5 "2018-08-28T17:58:50Z")

</div>

Can you show your elasticsearch log around the time it goes down?

---

<div class="post-metadata">

**Author:** ![jesusgn90](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jesusgn90/32/26998_2.png) [@jesusgn90](https://discuss.elastic.co/u/jesusgn90)\
**Post date:** [August 28, 2018, 6:31pm UTC](https://discuss.elastic.co/t/elasticsearch-down-after-plugin-installation/146319/6 "2018-08-28T18:31:28Z")

</div>

Ok @rjernst after some research I've found the cause from this situation. An out of memory error:

```auto
Aug 28 18:24:48 localhost.localdomain kernel: Out of memory: Kill process 1122 (java) score 255 or sacrifice child
Aug 28 18:24:48 localhost.localdomain kernel: Killed process 1122 (java) total-vm:4832964kB, anon-rss:459236kB, file-rss:0kB, shmem-rss:0kB
Aug 28 18:24:48 localhost.localdomain systemd[1]: elasticsearch.service: main process exited, code=killed, status=9/KILL
Aug 28 18:24:48 localhost.localdomain systemd[1]: Unit elasticsearch.service entered failed state.
Aug 28 18:24:48 localhost.localdomain systemd[1]: elasticsearch.service failed.

```

The optimizing procedure has a RAM peak and it causes Elasticsearch being killed. The machine was a bit overloaded so I understand it's not an error itself. Now my question is why is Elasticsearch the target to be killed instead other components or other installed software?

Regards

---

<div class="post-metadata">

**Author:** ![rjernst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rjernst/32/6363_2.png) [@rjernst](https://discuss.elastic.co/u/rjernst)\
**Post date:** [August 28, 2018, 8:32pm UTC](https://discuss.elastic.co/t/elasticsearch-down-after-plugin-installation/146319/7 "2018-08-28T20:32:47Z")

</div>

This reason would be platform dependent, but most likely elasticsearch is the highest user of memory on the system, so a prime target for the OOM killer when there is memory pressure.

---

<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:** [September 25, 2018, 8:32pm UTC](https://discuss.elastic.co/t/elasticsearch-down-after-plugin-installation/146319/8 "2018-09-25T20:32:49Z")

</div>

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