# Elasticsearch Failed with signal

**URL:** <https://discuss.elastic.co/t/elasticsearch-failed-with-signal/260975>\
**Category:** Elasticsearch\
**Created:** [January 13, 2021, 10:42am UTC](https://discuss.elastic.co/t/elasticsearch-failed-with-signal/260975 "2021-01-13T10:42:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joegio](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@Joegio](https://discuss.elastic.co/u/Joegio)\
**Post date:** [January 13, 2021, 10:42am UTC](https://discuss.elastic.co/t/elasticsearch-failed-with-signal/260975/1 "2021-01-13T10:42:44Z")

</div>

Good Morning, i'm newbie with elasticsearch.  
I have installed zammad on the our server with elasticsearch.  
ES service running but after about one hour has been killed with result 'signal'.  
I have tried to change configuration file:  
uncomment bootstrapmememorylock=true  
uncomment maxlockedmemory=unlimited  
Thank You for support  
Best Regards

---

<div class="post-metadata">

**Author:** ![Joegio](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@Joegio](https://discuss.elastic.co/u/Joegio)\
**Post date:** [January 13, 2021, 1:07pm UTC](https://discuss.elastic.co/t/elasticsearch-failed-with-signal/260975/2 "2021-01-13T13:07:08Z")

</div>

The error has been caused by swap memory of the server.  
I have tried this solution [Disable swapping | Elasticsearch Reference [5.5] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/setup-configuration-memory.html) and now the service running.

---

<div class="post-metadata">

**Author:** ![Joegio](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@Joegio](https://discuss.elastic.co/u/Joegio)\
**Post date:** [January 14, 2021, 4:44pm UTC](https://discuss.elastic.co/t/elasticsearch-failed-with-signal/260975/3 "2021-01-14T16:44:10Z")

</div>

Today elasticsearch has been crashed again.

 ![Schermata 2021-01-14 alle 17.19.53](https://us1.discourse-cdn.com/elastic/original/3X/7/1/7149f1e6f021e7dd03f7acc6541267ef0485650a.png)

Thank You

---

<div class="post-metadata">

**Author:** ![HenningAndersen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/henningandersen/32/48188_2.png) [@HenningAndersen](https://discuss.elastic.co/u/HenningAndersen)\
**Post date:** [January 18, 2021, 6:49pm UTC](https://discuss.elastic.co/t/elasticsearch-failed-with-signal/260975/4 "2021-01-18T18:49:14Z")

</div>

Hi @Joegio,

are you using a version 5.5 of Elasticsearch or are you on a more recent version?

The last "crash" looks like the host/container running Elasticsearch ran out of native memory (or some other resource), causing Elasticsearch to fail (we need threads). Perhaps you can assign more resources to the container?

---

<div class="post-metadata">

**Author:** ![Joegio](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@Joegio](https://discuss.elastic.co/u/Joegio)\
**Post date:** [January 19, 2021, 8:09am UTC](https://discuss.elastic.co/t/elasticsearch-failed-with-signal/260975/5 "2021-01-19T08:09:15Z")

</div>

Thank You for your answer...

I have installed elasticsearch 5.5 with zammad...

Yes, the problem has been caused by RAM...

Infact I have increased Ram and now the elasticsearch process running correctly..

Thank You

---

<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:** [February 16, 2021, 8:09am UTC](https://discuss.elastic.co/t/elasticsearch-failed-with-signal/260975/6 "2021-02-16T08:09:35Z")

</div>

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