[as next] (http://192.168.240.8:5601/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:338:774903)
at s (http://192.168.240.8:5601/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:338:774546)
at t (http://192.168.240.8:5601/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:338:775041)
at http://192.168.240.8:5601/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:338:775191
```
jvm.options
```auto
## GC configuration
8-13:-XX:+UseConcMarkSweepGC
8-13:-XX:CMSInitiatingOccupancyFraction=75
8-13:-XX:+UseCMSInitiatingOccupancyOnly
## G1GC Configuration
14-:-XX:+UseG1GC
14-:-XX:G1ReservePercent=25
14-:-XX:InitiatingHeapOccupancyPercent=30
## JVM temporary directory
-Djava.io.tmpdir=${ES_TMPDIR}
## heap dumps
-XX:+HeapDumpOnOutOfMemoryError
# specify an alternative path for heap dumps; ensure the directory exists and
# has sufficient space
-XX:HeapDumpPath=/var/lib/elasticsearch
# specify an alternative path for JVM fatal error logs
-XX:ErrorFile=/var/log/elasticsearch/hs_err_pid%p.log
## JDK 8 GC logging
8:-XX:+PrintGCDetails
8:-XX:+PrintGCDateStamps
8:-XX:+PrintTenuringDistribution
8:-XX:+PrintGCApplicationStoppedTime
8:-Xloggc:/var/log/elasticsearch/gc.log
8:-XX:+UseGCLogFileRotation
8:-XX:NumberOfGCLogFiles=32
8:-XX:GCLogFileSize=64m
# JDK 9+ GC logging
9-:-Xlog:gc*,gc+age=trace,safepoint:file=/var/log/elasticsearch/gc.log:utctime,pid,tags:filecount=32,filesize=64m
```
I have tried 4Gs of heap space.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [July 16, 2020, 1:47am UTC](https://discuss.elastic.co/t/elk-7-6-0-1-kibana/241378/2 "2020-07-16T01:47:11Z")
Welcome to our community! 😃
Can you please edit your post and format your code/logs/config using the `` button, or markdown style back ticks. It helps to make things easy to read which helps us help you
---
### Author:  [@SteveHodges](https://discuss.elastic.co/u/SteveHodges)
#### Post date: [July 16, 2020, 9:51pm UTC](https://discuss.elastic.co/t/elk-7-6-0-1-kibana/241378/3 "2020-07-16T21:51:33Z")
Changes made.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [July 16, 2020, 10:36pm UTC](https://discuss.elastic.co/t/elk-7-6-0-1-kibana/241378/4 "2020-07-16T22:36:20Z")
> [@SteveHodges](#):
>
> `Data too large, data for []`
That's unusual, what sort of request are you making when you get that?
---
### Author:  [@SteveHodges](https://discuss.elastic.co/u/SteveHodges)
#### Post date: [July 17, 2020, 10:08pm UTC](https://discuss.elastic.co/t/elk-7-6-0-1-kibana/241378/5 "2020-07-17T22:08:31Z")
I get the error when going to the home page for Kibana or to Management\Reporting. If I wait long enough the pages will refresh and come up
```auto
{"statusCode":500,"error":"Internal Server Error","message":"[parent] Data too large, data for [] would be [3111479034/2.8gb], which is larger than the limit of [2993920409/2.7gb], real usage: [3111478520/2.8gb], new bytes reserved: [514/514b], usages [request=0/0b, fielddata=22647/22.1kb, in_flight_requests=514/514b, accounting=607730233/579.5mb]: [circuit_breaking_exception] [parent] Data too large, data for [] would be [3111479034/2.8gb], which is larger than the limit of [2993920409/2.7gb], real usage: [3111478520/2.8gb], new bytes reserved: [514/514b], usages [request=0/0b, fielddata=22647/22.1kb, in_flight_requests=514/514b, accounting=607730233/579.5mb], with { bytes_wanted=3111479034 & bytes_limit=2993920409 & durability=\"PERMANENT\" }"}
```
Often I am just running daily and weekly reports for Auditbeat, filebeat, or winlog beat with searches like this
```auto
event.outcome : success and event.action:user_login or event.outcome : success and event.action:"Started-Session"
```
It sometime gives the following error
```auto
SyntaxError: Unexpected token u in JSON at position 0
at JSON.parse ()
at http://10.134.90.8:5601/bundles/commons.bundle.js:3:3378900
at http://10.134.90.8:5601/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:368:94842
at http://10.134.90.8:5601/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:368:94980
at u.$digest (http://10.134.90.8:5601/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:368:100155)
at http://10.134.90.8:5601/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:368:102127
at Yo.completeTask (http://10.134.90.8:5601/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:368:122692)
at http://10.134.90.8:5601/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:368:34257
```
Generating CSV often will also give the error `"Reporting Error: Not Found"`
Today it has been failing more consistently.
---
### Author:  [@SteveHodges](https://discuss.elastic.co/u/SteveHodges)
#### Post date: [July 20, 2020, 5:59pm UTC](https://discuss.elastic.co/t/elk-7-6-0-1-kibana/241378/6 "2020-07-20T17:59:36Z")
It seems to be definitely a resources issue. On the ELK server I turned of auditbeat, filebeat, and logstash. The Kibana reporting was working perfectly fine now.
That leads me to ask the following questions:
1. if we turn off logstash are we losing logs?
2. For the 40 auditbeat and filebeat agents I using the default settings for how often it sends the logs. Is there a better setting I should be using?
3. Is version 7.8 more resource friendly?
---
### Author:  [@SteveHodges](https://discuss.elastic.co/u/SteveHodges)
#### Post date: [July 27, 2020, 8:20pm UTC](https://discuss.elastic.co/t/elk-7-6-0-1-kibana/241378/7 "2020-07-27T20:20:43Z")
The issue is back even with Logstash turned off. I am getting this error
```auto
{"statusCode":500,"error":"Internal Server Error","message":"[parent] Data too large, data for [] would be [3101900416/2.8gb], which is larger than the limit of [2993920409/2.7gb], real usage: [3101900416/2.8gb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=22866/22.3kb, in_flight_requests=0/0b, accounting=613438772/585mb]: [circuit_breaking_exception] [parent] Data too large, data for [] would be [3101900416/2.8gb], which is larger than the limit of [2993920409/2.7gb], real usage: [3101900416/2.8gb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=22866/22.3kb, in_flight_requests=0/0b, accounting=613438772/585mb], with { bytes_wanted=3101900416 & bytes_limit=2993920409 & durability=\"PERMANENT\" }"}
```
When just going to Kibana's home page
```auto
http://127.0.0.1:5601/app/kibana
```
When I do top elasticsearch VIRT column is huge. 238G. How can I troubleshoot why elasticsearch is using so much memory. RES is 3.5G and there is only 8 gigs of physical memory.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 24, 2020, 8:34pm UTC](https://discuss.elastic.co/t/elk-7-6-0-1-kibana/241378/8 "2020-08-24T20:34:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.