# Kibana throws a "oops message **URL:** \ **Category:** Kibana\ **Created:** [September 19, 2018, 9:17am UTC](https://discuss.elastic.co/t/kibana-throws-a-oops-message/149091 "2018-09-19T09:17:26Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Carlos\_Magalhaes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_magalhaes/32/74604_2.png) [@Carlos\_Magalhaes](https://discuss.elastic.co/u/Carlos_Magalhaes)\ **Post date:** [September 19, 2018, 9:17am UTC](https://discuss.elastic.co/t/kibana-throws-a-oops-message/149091/1 "2018-09-19T09:17:26Z")
I am using Kibana to display dashboards for my firewall logs. There is more than enough memory, cpu and space on the machine it is running on. Randomly I get a Oops or Refresh message that asks to refresh the page and has an error of: ``` Courier fetch: Request Timeout after 30000ms Version: 6.4.0 Build: 17929 Error: Request Timeout after 30000ms at http://x.x.x.x:5601/bundles/vendors.bundle.js:313:150014 at http://x.x.x.x:5601/bundles/vendors.bundle.js:313:150447 ``` I can confirm that on the network testing with ifperf there is no issue the machine is connected to the main switch at 10gbps and the firewall is connected to the same switch at 10gbps Any idea what I am doing wrong or what I can change to avoid this. To be clear if I refresh the page it goes all back to normal. ---
**Author:** ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)\ **Post date:** [September 19, 2018, 3:24pm UTC](https://discuss.elastic.co/t/kibana-throws-a-oops-message/149091/2 "2018-09-19T15:24:04Z")
Any idea what queries are causing this request timeout? It's possible that if you have a very large dashboard or an ill-crafted query, then this could be caused simply by the amount of time it takes for Elasticsearch to collect all of the data associated with the request. ---
**Author:** ![Carlos\_Magalhaes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_magalhaes/32/74604_2.png) [@Carlos\_Magalhaes](https://discuss.elastic.co/u/Carlos_Magalhaes)\ **Post date:** [September 19, 2018, 4:29pm UTC](https://discuss.elastic.co/t/kibana-throws-a-oops-message/149091/3 "2018-09-19T16:29:54Z")
Thank you @lukas I will wait on the error to happen again and will point. I don't recall it specifying a query but I could be wrong and I will confirm. On the dashboard - yes its a large dashboard being updated every 5 minutes. There are normal vertical bar graphs, x2 heat maps on a world map. Basically its this dashboard: ![](https://i1.wp.com/extelligenceblog.it/wp-content/uploads/2017/07/AlertsDashboard.png) ---
**Author:** ![Carlos\_Magalhaes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_magalhaes/32/74604_2.png) [@Carlos\_Magalhaes](https://discuss.elastic.co/u/Carlos_Magalhaes)\ **Post date:** [September 19, 2018, 10:17pm UTC](https://discuss.elastic.co/t/kibana-throws-a-oops-message/149091/4 "2018-09-19T22:17:19Z")
@lukas ok it happened and I managed to catch the full error: Courier fetch: unknown error Version: 6.4.0 Build: 17929 Error: unknown error at respond ([http://X.X.X.X:5601/bundles/vendors.bundle.js:313:149441](http://X.X.X.X:5601/bundles/vendors.bundle.js:313:149441)) at checkRespForFailure ([http://X.X.X.X:5601/bundles/vendors.bundle.js:313:148589](http://X.X.X.X:5601/bundles/vendors.bundle.js:313:148589)) at [http://X.X.X.X:5601/bundles/vendors.bundle.js:313:157823](http://X.X.X.X:5601/bundles/vendors.bundle.js:313:157823) at processQueue ([http://X.X.X.X:5601/bundles/vendors.bundle.js:197:199684](http://X.X.X.X:5601/bundles/vendors.bundle.js:197:199684)) at [http://x.x.x.x:5601/bundles/vendors.bundle.js:197:200647](http://x.x.x.x:5601/bundles/vendors.bundle.js:197:200647) at Scope.$digest ([http://x.x.x.x:5601/bundles/vendors.bundle.js:197:210409](http://x.x.x.x:5601/bundles/vendors.bundle.js:197:210409)) at Scope.$apply ([http://x.x.x.x:5601/bundles/vendors.bundle.js:197:213216](http://x.x.x.x:5601/bundles/vendors.bundle.js:197:213216)) at done ([http://x.x.x.x:5601/bundles/vendors.bundle.js:197:132715](http://x.x.x.x:5601/bundles/vendors.bundle.js:197:132715)) at completeRequest ([http://x.x.x.x:5601/bundles/vendors.bundle.js:197:136327](http://x.x.x.x:5601/bundles/vendors.bundle.js:197:136327)) at XMLHttpRequest.requestError ([http://x.x.x.x:5601/bundles/vendors.bundle.js:197:135344](http://x.x.x.x:5601/bundles/vendors.bundle.js:197:135344)) Fatal Error Uncaught IndexSizeError: Failed to execute 'getImageData' on 'CanvasRenderingContext2D': The source width is 0. ([http://x.x.x.x:5601/bundles/vendors.bundle.js:78](http://x.x.x.x:5601/bundles/vendors.bundle.js:78)) Version: 6.4.0 Build: 17929 Error: Uncaught IndexSizeError: Failed to execute 'getImageData' on 'CanvasRenderingContext2D': The source width is 0. ([http://x.x.x.x:5601/bundles/vendors.bundle.js:78](http://x.x.x.x:5601/bundles/vendors.bundle.js:78)) at window.onerror ([http://x.x.x.x:5601/bundles/commons.bundle.js:3:768238](http://x.x.x.x:5601/bundles/commons.bundle.js:3:768238) ---
**Author:** ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)\ **Post date:** [September 19, 2018, 10:40pm UTC](https://discuss.elastic.co/t/kibana-throws-a-oops-message/149091/5 "2018-09-19T22:40:52Z")
When the error happened was there a specific visualization that wasn't showing up? ---
**Author:** ![Carlos\_Magalhaes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_magalhaes/32/74604_2.png) [@Carlos\_Magalhaes](https://discuss.elastic.co/u/Carlos_Magalhaes)\ **Post date:** [September 20, 2018, 5:29am UTC](https://discuss.elastic.co/t/kibana-throws-a-oops-message/149091/6 "2018-09-20T05:29:56Z")
Sure and thank you ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 18, 2018, 5:29am UTC](https://discuss.elastic.co/t/kibana-throws-a-oops-message/149091/7 "2018-10-18T05:29:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.