# \[NodeJS\] Error socket hang up, No Living connections

**URL:** <https://discuss.elastic.co/t/nodejs-error-socket-hang-up-no-living-connections/170025>\
**Category:** Elasticsearch\
**Created:** [February 26, 2019, 2:41pm UTC](https://discuss.elastic.co/t/nodejs-error-socket-hang-up-no-living-connections/170025 "2019-02-26T14:41:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lfallet](https://avatars.discourse-cdn.com/v4/letter/l/71e660/32.png) [@lfallet](https://discuss.elastic.co/u/lfallet)\
**Post date:** [February 26, 2019, 2:41pm UTC](https://discuss.elastic.co/t/nodejs-error-socket-hang-up-no-living-connections/170025/1 "2019-02-26T14:41:18Z")

</div>

Elasticsearch version : 6.4.3, deployed in ElasticCloud  
Elasticsearch Node package version : 15.2.0

We're experiencing recurring errors:

```
Elasticsearch ERROR: 2019-02-26T13:31:11Z
  Error: Request error, retrying
  POST https://xxx.gcp.cloud.es.io:9243/a_comment/comment/_search => socket hang up
      at Log.error (/app/node_modules/elasticsearch/src/lib/log.js:226:56)
      at checkRespForFailure (/app/node_modules/elasticsearch/src/lib/transport.js:259:18)
      at HttpConnector.<anonymous> (/app/node_modules/elasticsearch/src/lib/connectors/http.js:163:7)
      at ClientRequest.wrapper (/app/node_modules/lodash/lodash.js:4935:19)
      at emitOne (events.js:121:20)
      at ClientRequest.emit (events.js:211:7)
      at TLSSocket.socketOnEnd (_http_client.js:423:9)
      at emitNone (events.js:111:20)
      at TLSSocket.emit (events.js:208:7)
      at endReadableNT (_stream_readable.js:1064:12)
      at _combinedTickCallback (internal/process/next_tick.js:138:11)
      at process._tickCallback (internal/process/next_tick.js:180:9)

 warn: [ESService.find] No Living connections
error: [CommentService.find] No Living connections

```

Are those error usual?  
Is retrying a normal process with a decently sized cluster (3 nodes, 8Gb RAM for less than 5000 documents indexed) ?  
Is there a specific configuration for NodeJS 8 ?  
How could I investigate about the pool, how old connections are?

Regards,  
Laurent

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 8, 2019, 9:05am UTC](https://discuss.elastic.co/t/nodejs-error-socket-hang-up-no-living-connections/170025/2 "2019-03-08T09:05:01Z")

</div>

@spalger Do you think you can help here?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 5, 2019, 9:05am UTC](https://discuss.elastic.co/t/nodejs-error-socket-hang-up-no-living-connections/170025/3 "2019-04-05T09:05:03Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.