# Kibana Status goes Red quite often with Socket hang up **URL:** \ **Category:** Kibana\ **Created:** [February 3, 2022, 3:43pm UTC](https://discuss.elastic.co/t/kibana-status-goes-red-quite-often-with-socket-hang-up/296211 "2022-02-03T15:43:02Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![adityak248](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@adityak248](https://discuss.elastic.co/u/adityak248)\ **Post date:** [February 3, 2022, 3:43pm UTC](https://discuss.elastic.co/t/kibana-status-goes-red-quite-often-with-socket-hang-up/296211/1 "2022-02-03T15:43:02Z")
Hello, I am running elastic 5.5.2 Kibana goes to red quite often `curl -XGET http://localhost:9200/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip?v wont respond ` and even elasticsearh cluster wont respond with `curl -XGET http://localhost:9200/_cat/nodes?v` Everything starts to work only after master is restarted. I see socket time out on kibana console. ```auto ### Status Breakdown |ID|Status| | --- | --- | |ui settings|Elasticsearch plugin is red| |plugin:kibana@5.5.2|Ready| |plugin:elasticsearch@5.5.2|{"code":"ECONNRESET"}| |plugin:xpack_main@5.5.2|socket hang up| |plugin:monitoring@5.5.2|Ready| |plugin:searchprofiler@5.5.2|socket hang up| |plugin:tilemap@5.5.2|socket hang up| |plugin:watcher@5.5.2|socket hang up| |plugin:grokdebugger@5.5.2|Ready| |plugin:metrics@5.5.2|Ready| |plugin:timelion@5.5.2|Ready| ``` Cluster setup kibana 1 coordinator node 5 data nodes ---
**Author:** ![adityak248](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@adityak248](https://discuss.elastic.co/u/adityak248)\ **Post date:** [February 3, 2022, 3:59pm UTC](https://discuss.elastic.co/t/kibana-status-goes-red-quite-often-with-socket-hang-up/296211/2 "2022-02-03T15:59:18Z")
Here are my kibana and elastic configurations ```auto logging.dest: /var/log/kibana/kibana.stdout server.port: 5601 server.host: "0.0.0.0" elasticsearch.url: "http://localhost:9200" elasticsearch.requestTimeout: 300000 xpack.security.enabled: false xpack.monitoring.enabled: true xpack.graph.enabled: false xpack.reporting.enabled: false xpack.ml.enabled: false console.enabled: false ``` and elastic.yml ```auto cluster.name: log-cluster discovery.zen.minimum_master_nodes: 3 discovery.zen.ping.unicast.hosts: - elastic1.internal:9300 - elastic2.internal:9300 - elastic3.internal:9300 - elastic4.internal:9300 - elastic5.internal:9300 network.host: [_local_,_site_] network.publish_host: _site_ search: remote: logging: seeds: - elastic1.internal:9300 - elastic2.internal:9300 - elastic3.internal:9300 - elastic4.internal:9300 - elastic5.internal:9300 node.name: ${HOSTNAME} node.master: false node.data: false node.ingest: false node.ml: false path.logs: /db/elastic/log path.data: /db/elastic/data bootstrap.memory_lock: true bootstrap.seccomp: false xpack.security.enabled: false xpack.monitoring.enabled: true xpack.graph.enabled: false xpack.watcher.enabled: false xpack.ml.enabled: false ``` ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [February 3, 2022, 5:19pm UTC](https://discuss.elastic.co/t/kibana-status-goes-red-quite-often-with-socket-hang-up/296211/3 "2022-02-03T17:19:13Z")
Hello, We don't support 5.5.2 anymore and our latest release is 7.17. Please see this product end of lifes here. > **[Elastic product end of life dates | Elastic](https://www.elastic.co/support/eol)** So I am not sure how to get you the help you need. Are you ok to upgrade? Thanks, Bhavya ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 3, 2022, 5:19pm UTC](https://discuss.elastic.co/t/kibana-status-goes-red-quite-often-with-socket-hang-up/296211/4 "2022-03-03T17:19:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.