# ES dies continuously after upgrade from 2.0.1 to 2.1.0

**URL:** <https://discuss.elastic.co/t/es-dies-continuously-after-upgrade-from-2-0-1-to-2-1-0/36542>\
**Category:** Elasticsearch\
**Created:** [December 7, 2015, 2:57pm UTC](https://discuss.elastic.co/t/es-dies-continuously-after-upgrade-from-2-0-1-to-2-1-0/36542 "2015-12-07T14:57:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcosangalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcosangalli/32/6465_2.png) [@marcosangalli](https://discuss.elastic.co/u/marcosangalli)\
**Post date:** [December 7, 2015, 2:57pm UTC](https://discuss.elastic.co/t/es-dies-continuously-after-upgrade-from-2-0-1-to-2-1-0/36542/1 "2015-12-07T14:57:46Z")

</div>

Four days ago I upgraded (with apt-get) from 2.0.1. to 2.1.0 my single node elastic search on ubuntu in aws. After the upgrade system continuously die after minutes without any message in the logs. After several probes, I tried it in a new fresh 2.1.0 host, without any results: system crash again!

After I saw that the snapshot/restore are not compatible from 2.1.0 to 2.0.1 I done a full reindex of data in a fresh 2.0.1 ES and now is stable again.

Did you have any suggestion?

Thank you in advance, marco

---

<div class="post-metadata">

**Author:** ![msimos](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@msimos](https://discuss.elastic.co/u/msimos)\
**Post date:** [December 8, 2015, 12:47am UTC](https://discuss.elastic.co/t/es-dies-continuously-after-upgrade-from-2-0-1-to-2-1-0/36542/2 "2015-12-08T00:47:51Z")

</div>

Hi,

I'd recommend you enable DEBUG logging in logging.yml by setting `es.logger.level: DEBUG`. Then restart Elasticsearch and check the Elasticsearch log file for any errors. I'd also check /var/log/messages for any errors there.

---

<div class="post-metadata">

**Author:** ![marcosangalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcosangalli/32/6465_2.png) [@marcosangalli](https://discuss.elastic.co/u/marcosangalli)\
**Post date:** [December 8, 2015, 8:34am UTC](https://discuss.elastic.co/t/es-dies-continuously-after-upgrade-from-2-0-1-to-2-1-0/36542/3 "2015-12-08T08:34:22Z")

</div>

Hi Mike,

thank you for your reply. I'll try to reproduce the problem on a test system with DEBUG enabled. After 24h rollback to 2.0.1 (without any application changes) the system runs without any problem.

---

<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:** [December 8, 2015, 8:47am UTC](https://discuss.elastic.co/t/es-dies-continuously-after-upgrade-from-2-0-1-to-2-1-0/36542/4 "2015-12-08T08:47:33Z")

</div>

If you can reproduce it with logs and details, please open an issue for it.

---

<div class="post-metadata">

**Author:** ![marcosangalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcosangalli/32/6465_2.png) [@marcosangalli](https://discuss.elastic.co/u/marcosangalli)\
**Post date:** [December 8, 2015, 9:38am UTC](https://discuss.elastic.co/t/es-dies-continuously-after-upgrade-from-2-0-1-to-2-1-0/36542/5 "2015-12-08T09:38:25Z")

</div>

Hi David,

I'll try. I saw another side effect in these days related with this instability: when I tried to restart ES I had the cpu at 100% and then I had to kill the process with -9. I have the logs for that: [http://pastebin.com/S1KqALrn](http://pastebin.com/S1KqALrn)

---

<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:** [July 5, 2017, 11:32pm UTC](https://discuss.elastic.co/t/es-dies-continuously-after-upgrade-from-2-0-1-to-2-1-0/36542/6 "2017-07-05T23:32:42Z")

</div>