# Socket hang up kibana **URL:** \ **Category:** Kibana\ **Created:** [June 12, 2018, 7:41pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591 "2018-06-12T19:41:59Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![meetdave2611997](https://avatars.discourse-cdn.com/v4/letter/m/f07891/32.png) [@meetdave2611997](https://discuss.elastic.co/u/meetdave2611997)\ **Post date:** [June 12, 2018, 7:42pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591/1 "2018-06-12T19:42:00Z")
Hello, Kibana is throwing socket hang up exception very frequently and because of this problem kibana is unable to serve any search request. Every time due to below error socket hang up error occurs. ``` {"type":"log","@timestamp":"2018-06-12T00:01:07Z","tags":["error","elasticsearch","admin"],"pid":11447,"message":"Request error, retrying\nPOST https://x.x.x.x:9200/_xpack/monitoring/_bulk?system_id=kibana&system_api_version=2&interval=10000ms => socket hang up ``` How do we prevent this error? Thanks! ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [June 13, 2018, 1:20pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591/2 "2018-06-13T13:20:00Z")
Hey @meetdave2611997 can you check your Elasticsearch logs to see if any errors are being logged? It appears that monitoring is having issues communicating with your Elasticcsearch cluster, or the calls are taking too long. ---
**Author:** ![meetdave2611997](https://avatars.discourse-cdn.com/v4/letter/m/f07891/32.png) [@meetdave2611997](https://discuss.elastic.co/u/meetdave2611997)\ **Post date:** [June 13, 2018, 1:32pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591/3 "2018-06-13T13:32:11Z")
@Brandon_Kobel There is no logs on elasticsearch side when this error occurs ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [June 13, 2018, 1:33pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591/4 "2018-06-13T13:33:59Z")
@meetdave2611997 are you using a dedicated Elasticsearch cluster for your monitoring data? If you are, you should see `xpack.monitoring.elasticsearch.url` set in your `kibana.yml` ---
**Author:** ![meetdave2611997](https://avatars.discourse-cdn.com/v4/letter/m/f07891/32.png) [@meetdave2611997](https://discuss.elastic.co/u/meetdave2611997)\ **Post date:** [June 13, 2018, 1:35pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591/5 "2018-06-13T13:35:45Z")
@Brandon_Kobel No we are not using dedicated monitoring cluster. Same cluster is being used for monitoring purpose ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [June 13, 2018, 1:46pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591/6 "2018-06-13T13:46:05Z")
Hey @meetdave2611997 can you share your relevant Kibana and Elasticsearch logs? ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [June 13, 2018, 2:32pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591/7 "2018-06-13T14:32:52Z")
Also, do you have a proxy in-front of Elasticsearch? Does everything else in Kibana seem to functional normally? ---
**Author:** ![meetdave2611997](https://avatars.discourse-cdn.com/v4/letter/m/f07891/32.png) [@meetdave2611997](https://discuss.elastic.co/u/meetdave2611997)\ **Post date:** [June 13, 2018, 2:47pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591/8 "2018-06-13T14:47:55Z")
@Brandon_Kobel Yes, we do have a load balancer in-front of Elasticsearch. We can navigate each page in kibana but kibana is not showing any results. Every time we need to restart kibana and when we restart it, it works fine utill another socket hang up error occurs. ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [June 13, 2018, 2:57pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591/9 "2018-06-13T14:57:06Z")
@meetdave2611997 from your description, it sounds like Kibana is having issues communicating with Elasticsearch in general, could you try pointing Kibana directly at an instance (removing the load balancer) to see if it starts working? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 11, 2018, 2:57pm UTC](https://discuss.elastic.co/t/socket-hang-up-kibana/135591/10 "2018-07-11T14:57:15Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.