# Kibana 4.3.1 died with process out of memory

**URL:** <https://discuss.elastic.co/t/kibana-4-3-1-died-with-process-out-of-memory/42152>\
**Category:** Kibana\
**Created:** [February 18, 2016, 3:35pm UTC](https://discuss.elastic.co/t/kibana-4-3-1-died-with-process-out-of-memory/42152 "2016-02-18T15:35:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![skynardo](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@skynardo](https://discuss.elastic.co/u/skynardo)\
**Post date:** [February 18, 2016, 3:35pm UTC](https://discuss.elastic.co/t/kibana-4-3-1-died-with-process-out-of-memory/42152/1 "2016-02-18T15:35:42Z")

</div>

I have a new ELK server running on RHEL 6 that I am starting to ramp up sending application log files to (approx 7Gb/day so far). I found that my Kibana server died yesterday with the following error in stderr:  
chroot: cannot change root directory to : No such file or directory  
chroot: cannot change root directory to : No such file or directory  
Debug: internal, implementation, error  
Error: ENOSPC, no space left on device  
at Error (native)  
at Object.fs.writeSync (fs.js:613:20)  
at SyncWriteStream.write (fs.js:1856:6)  
at KbnLoggerJsonFormat.ondata (\_stream\_readable.js:540:20)  
at KbnLoggerJsonFormat.emit (events.js:107:17)  
at readableAddChunk (\_stream\_readable.js:163:16)  
at KbnLoggerJsonFormat.Readable.push (\_stream\_readable.js:126:10)  
at KbnLoggerJsonFormat.Transform.push (\_stream\_transform.js:140:32)  
at KbnLoggerJsonFormat.\_transform (/opt/kibana/src/server/logging/LogFormat.js:61:12)  
at KbnLoggerJsonFormat.Transform.\_read (\_stream\_transform.js:179:10)  
at KbnLoggerJsonFormat.Transform.\_write (\_stream\_transform.js:167:12)  
at doWrite (\_stream\_writable.js:301:12)  
at writeOrBuffer (\_stream\_writable.js:288:5)  
at KbnLoggerJsonFormat.Writable.write (\_stream\_writable.js:217:11)  
at [object Object].ondata (\_stream\_readable.js:540:20)  
at [object Object].emit (events.js:107:17)  
FATAL ERROR: CALL\_AND\_RETRY\_LAST Allocation failed - process out of memory

I don't see any evidence of swapping or high CPU on the machine a this time. I do see where an attempt to write a coredump to /var failed due to lack of space in that filesystem. ( I have expanded /var )

snippet from /var/log/messages:  
Feb 17 09:49:01 dsa528 abrt[2446]: Write error: No space left on device  
Feb 17 09:49:02 dsa528 abrt[2446]: Error writing '/var/spool/abrt/ccpp-2016-02-17-09:48:47-59476.new/coredump'

Are there any tuning suggestions or other things I should be watching to determine what caused this?

---

<div class="post-metadata">

**Author:** ![mnhan](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@mnhan](https://discuss.elastic.co/u/mnhan)\
**Post date:** [February 18, 2016, 3:45pm UTC](https://discuss.elastic.co/t/kibana-4-3-1-died-with-process-out-of-memory/42152/2 "2016-02-18T15:45:05Z")

</div>

see if setting --max-old-space-size= help in keeping kibana from running the server out of ram. Kibana's node.js leaks memory. see [Kibana 4.2 server memory usage](https://discuss.elastic.co/t/kibana-4-2-server-memory-usage/33575/13) and the issue listed in the post on git.

---

<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:** [July 6, 2017, 2:01pm UTC](https://discuss.elastic.co/t/kibana-4-3-1-died-with-process-out-of-memory/42152/3 "2017-07-06T14:01:54Z")

</div>