# Node dont start after server crash

**URL:** <https://discuss.elastic.co/t/node-dont-start-after-server-crash/278204>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [July 8, 2021, 3:12pm UTC](https://discuss.elastic.co/t/node-dont-start-after-server-crash/278204 "2021-07-08T15:12:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [July 8, 2021, 3:12pm UTC](https://discuss.elastic.co/t/node-dont-start-after-server-crash/278204/1 "2021-07-08T15:12:35Z")

</div>

We run ES 7.13.2 on k8s, with Docker engine. This is simple 3 nodes cluster with 10 indices and less than 100Go of data.

The ES cluster is used to monitore another ES cluster which is working fine (via metricbeat).

Our super infra team have restarted all Docker engine at same time ....

Now, all ES pod container are throwing:

```auto
Failed to submit a listener notification task. Event loop shut down?

```

Most of the time, I manually remove all pods, but now, I really want ES recover by it-self, is that possible?

![Capture d’écran 2021-07-08 à 17.10.51](https://us1.discourse-cdn.com/elastic/original/3X/1/f/1fb9082e606406468849a57543a487f5b0975af2.png)

Full logs here: [elasticsearch crash · GitHub](https://gist.github.com/ebuildy/3998b303f238943db2b8b44b78764995#file-elasticsearch-log)

---

<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:** [August 5, 2021, 3:12pm UTC](https://discuss.elastic.co/t/node-dont-start-after-server-crash/278204/2 "2021-08-05T15:12:42Z")

</div>

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