Kibana version:
Kibana 6.8.0
Elasticsearch version:
AWS ES/Kibana 6.8.0
Describe the bug:
SearchError: Request Entity Too Large
at https://name-domain.com/_plugin/kibana/bundles/kibana.bundle.js:2:583038
at processQueue (https://name-domain.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:199687)
at https://name-domain.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:200650
at Scope.$digest (https://name-domain.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:210412)
at Scope.$apply (https://name-domain.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:213219)
at done (https://name-domain.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:132717)
at completeRequest (https://name-domain.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:136329)
at XMLHttpRequest.requestLoaded (https://name-domain.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:135225)
Steps to reproduce:
- deploy the ES Kibana 6.8.0 in AWS
- deploy the Apache v2.4.46 in AWS EKS (and configure Kibana specific vhost config and Ingress)
- Hit Kibana in browser (chrome)
Expected behavior:
Should load the Kibana home page
Errors in browser console (if relevant):
This error occurs in the browser when hit the Kibana URL.
Provide logs and/or server output (if relevant):
Can not take the logs as the container has been restarted.
Any additional context:
We have not set LimitRequestBody in our config. Apache is deployed in AWS EKS as deployment/pods and seeing this error when Kibana url is accessed.
Question is, do we have to Set the LimitRequestBody for/specific to each vhost config to fix this error. We can not reproduce this error. Would like to know if there is any specific apache config on Limits/Directive's we have to set for Kibana?
i am seeing other errors like below too.
please suggest.