# Kibana interfaces took lots of time, restart the instance verything works fine **URL:** \ **Category:** Kibana\ **Created:** [November 6, 2019, 3:22am UTC](https://discuss.elastic.co/t/kibana-interfaces-took-lots-of-time-restart-the-instance-verything-works-fine/206713 "2019-11-06T03:22:20Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Joseph\_John](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joseph_john/32/53907_2.png) [@Joseph\_John](https://discuss.elastic.co/u/Joseph_John)\ **Post date:** [November 6, 2019, 3:22am UTC](https://discuss.elastic.co/t/kibana-interfaces-took-lots-of-time-restart-the-instance-verything-works-fine/206713/1 "2019-11-06T03:22:21Z")
Hi All, My elasticsearch environment is > apt list elasticsearch kibana filebeat auditbeat metricbeat > Listing... Done > **auditbeat/stable** ,now **7.4.2** amd64 [installed] > **elasticsearch/stable** ,now **7.4.2** amd64 [installed] > **filebeat** /stable,now **7.4.2** amd64 [installed] > **kibana** /stable,now **7.4.2** amd64 [installed] > **metricbeat** /stable,now **7.4.2** amd64 [installed] In my system I have maximum 7 or 8 system to be monitoring, I have decent elasticsearch server configuration, and my resource I find it is underused most of the time , so my hardware configuration is fine Now every day I find after some time of usage by kibana web interface, takes longer time to display the hostdetails, It gives this messages > Your visualization has error(s) > **Data Fetch Failure** > **Request Timeout after 30000ms** > "Your visualization has error(s)" + "Data Fetch Failure" + "Request Timeout after 30000ms" then I do restart my entire OS, then it works What may he the reason behind this behaviour ? My hardware details are > root@apmserver:~# lscpu > Architecture: x86\_64 > CPU op-mode(s): 32-bit, 64-bit > Byte Order: Little Endian > **CPU(s): 4** > On-line CPU(s) list: 0-3 > Thread(s) per core: 1 > Core(s) per socket: 2 > Socket(s): 2 > NUMA node(s): 1 > Vendor ID: GenuineIntel > CPU family: 6 > Model: 26 > Model name: \*\* Intel(R) Xeon(R) CPU E5520 @ 2.27GHz\*\* free -m > Mem total used free shared buff/cache available > Mem: 16040 3134 **10517** 13 2388 12593 > Swap: 4095 0 4095 thanks Joseph John ---
**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\ **Post date:** [November 11, 2019, 8:26pm UTC](https://discuss.elastic.co/t/kibana-interfaces-took-lots-of-time-restart-the-instance-verything-works-fine/206713/2 "2019-11-11T20:26:49Z")
Hello @Joseph_John Can you provide kibana and elasticsearch logs recorded when the error occurred? I'd like to figure out what request is timing out like that. Thanks, Matt ---
**Author:** ![Joseph\_John](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joseph_john/32/53907_2.png) [@Joseph\_John](https://discuss.elastic.co/u/Joseph_John)\ **Post date:** [November 14, 2019, 3:14am UTC](https://discuss.elastic.co/t/kibana-interfaces-took-lots-of-time-restart-the-instance-verything-works-fine/206713/3 "2019-11-14T03:14:43Z")
Thanks Mark, now I do not have the logs, I was trying out in a lab, exploring ELK, what I did when it was taking too much time I did reinstall, since it was not for production. Next time I see such behavior, I will post the logs with tagging this thread thanks for reaching out Joseph John ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 12, 2019, 3:14am UTC](https://discuss.elastic.co/t/kibana-interfaces-took-lots-of-time-restart-the-instance-verything-works-fine/206713/4 "2019-12-12T03:14:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.