Kibana - FATAL ERROR: Zone Allocation failed - process out of memory

Elastic Stack Kibana
1

Hello all,

Hope you are doing well! I have been struggling with starting Kibana server from yesterday. so after starting Elasticsearch cluster, when i start Kibana, it takes hours and gives me the following errors. can anyone please tell me how to fix it?

<--- Last few GCs --->

[434900:00000224EAF058B0]    22376 ms: Scavenge 23.1 (34.8) -> 16.5 (35.8) MB, 4.6 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure
[434900:00000224EAF058B0]    23612 ms: Scavenge 24.3 (35.8) -> 17.3 (36.3) MB, 4.2 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure
[434900:00000224EAF058B0]    24339 ms: Scavenge 27.2 (39.2) -> 20.4 (41.2) MB, 9.8 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure


<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 000003A964E5C5C1]
Security context: 0x007e2209e6c1 <JSObject>
    1: _compile [000000BF19AC52A1] [internal/modules/cjs/loader.js:723] [bytecode=000000BF19AD81B9 offset=151](this=0x01a9e1702689 <Module map = 000003F17EF34349>,content=0x006737102201 <Very long string[692361]>,filename=0x014d1896a659 <String[87]: C:\ELK7.9.2\kibana-7.9.2-windows-x86_64\node_modules\intl-relativeformat\lib\locales.js>)
    2: _compile [0...

FATAL ERROR: Zone Allocation failed - process out of memory
 1: 00007FF6AC79894A
 2: 00007FF6AC7733B6
 3: 00007FF6AC773D30
 4: 00007FF6ACA91F6E
 5: 00007FF6ACA91E9F
 6: 00007FF6ACC519B3
 7: 00007FF6ACC517F7
 8: 00007FF6ACAC7D55
 9: 00007FF6ACAC6515
10: 00007FF6ACACC05D
11: 00007FF6ACACB58D
12: 00007FF6ACACB3F9
13: 00007FF6ACACB1F7
14: 00007FF6ACACAAF1
15: 00007FF6ACACA6E4
16: 00007FF6ACAC9B6C
17: 00007FF6ACAC8C4A
18: 00007FF6ACAC7CD7
19: 00007FF6ACAC6515
20: 00007FF6ACACC05D
21: 00007FF6ACACB58D
22: 00007FF6ACACB3F9
23: 00007FF6ACACB1F7
24: 00007FF6ACACAAF1
25: 00007FF6ACACA6E4
26: 00007FF6ACAC9B6C
27: 00007FF6ACAC95B0
28: 00007FF6ACACB97D
29: 00007FF6ACACB3F9
30: 00007FF6ACACB1F7
31: 00007FF6ACACAAF1
32: 00007FF6ACACA6E4
33: 00007FF6ACAC9B6C
34: 00007FF6ACAC6B3F
35: 00007FF6ACAD195C
36: 00007FF6ACAD0E88
37: 00007FF6ACAD0654
38: 00007FF6ACAD02E0
39: 00007FF6ACD3E427
40: 00007FF6ACD3C2B8
41: 00007FF6ACD34A41
42: 00007FF6ACD34501
43: 00007FF6ACD34050
44: 00007FF6AD0117FB
45: 00007FF6ACC54F89
46: 00007FF6ACC57DE3
47: 00007FF6ACA9AF61
48: 00007FF6AC74933B
49: 00007FF6ACCA4A82
50: 00007FF6ACCA5F0D
51: 00007FF6ACCA4F66
52: 00007FF6ACCA4E4B
53: 000003A964E5C5C1

Thanks in advance!

2

Kibana doesn't have enough memory to run. One approach would be trying to give the VM/docker container more memory (in case you are running virtual) or move to another server with more memory if this is a bare metal setup.

How much memory does Kibana have to run? Is this the same system Elasticsearch is running on? If yes you have to make sure Elasticsearch is not using up all of the memory.

3

Okay. thank you Joe for the explanation.

4

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