# ELK 6.7.0. Server crashed by Kibana

**URL:** <https://discuss.elastic.co/t/elk-6-7-0-server-crashed-by-kibana/180607>\
**Category:** Kibana\
**Created:** [May 10, 2019, 6:19pm UTC](https://discuss.elastic.co/t/elk-6-7-0-server-crashed-by-kibana/180607 "2019-05-10T18:19:39Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marteen](https://avatars.discourse-cdn.com/v4/letter/m/ba9def/32.png) [@Marteen](https://discuss.elastic.co/u/Marteen)\
**Post date:** [May 10, 2019, 6:19pm UTC](https://discuss.elastic.co/t/elk-6-7-0-server-crashed-by-kibana/180607/1 "2019-05-10T18:19:39Z")

</div>

Hi.  
I run Kibana on a Chrome. I used the same 5601 port, however I use a server IP to be able to access Kibana from outside of localHost. the only products I use from ELK are: ElasticSearch, Kibana, FileLogBeats and WinLogBeats. and I send data from the host server and 2 other servers to the elasticsearch (I also use an open port for elasticsearch).

after about two weeks the server crashed due to high RAM consumption by Kibana. is there a way to prevent this by using any open source software? or windows configurations?

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [May 13, 2019, 3:38pm UTC](https://discuss.elastic.co/t/elk-6-7-0-server-crashed-by-kibana/180607/2 "2019-05-13T15:38:13Z")

</div>

Can you provide more details including the logs when Kibana crashed? Kibana generally uses under 400MB of RAM. Is that available on this machine?

---

<div class="post-metadata">

**Author:** ![Marteen](https://avatars.discourse-cdn.com/v4/letter/m/ba9def/32.png) [@Marteen](https://discuss.elastic.co/u/Marteen)\
**Post date:** [May 13, 2019, 6:59pm UTC](https://discuss.elastic.co/t/elk-6-7-0-server-crashed-by-kibana/180607/3 "2019-05-13T18:59:56Z")

</div>

I don't see any special logs under elasticsearch and none under kibana. yes I have enough ram on the server, however it spikes a lot.

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [May 13, 2019, 10:04pm UTC](https://discuss.elastic.co/t/elk-6-7-0-server-crashed-by-kibana/180607/4 "2019-05-13T22:04:12Z")

</div>

How are you starting Kibana? Is this on Linux? Are installing with a deb/rpm package?

---

<div class="post-metadata">

**Author:** ![Marteen](https://avatars.discourse-cdn.com/v4/letter/m/ba9def/32.png) [@Marteen](https://discuss.elastic.co/u/Marteen)\
**Post date:** [May 13, 2019, 10:13pm UTC](https://discuss.elastic.co/t/elk-6-7-0-server-crashed-by-kibana/180607/5 "2019-05-13T22:13:24Z")

</div>

It's on windows. Installed it as a service using nssm. And it's always in running state.

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [May 13, 2019, 10:14pm UTC](https://discuss.elastic.co/t/elk-6-7-0-server-crashed-by-kibana/180607/6 "2019-05-13T22:14:59Z")

</div>

I have never used NSSM. Is there a place that the STDOUT/STDERR for the service goes which you could check?

You could also enable monitoring in Kibana and look at the memory usage.

Do you have any 3rd party plugins installed?

---

<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:** [June 10, 2019, 10:15pm UTC](https://discuss.elastic.co/t/elk-6-7-0-server-crashed-by-kibana/180607/7 "2019-06-10T22:15:07Z")

</div>

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