# ES fell down and it can't get up
**URL:** https://discuss.elastic.co/t/es-fell-down-and-it-cant-get-up/23940
**Category:** Elasticsearch
**Created:** [June 18, 2015, 8:04pm UTC](https://discuss.elastic.co/t/es-fell-down-and-it-cant-get-up/23940 "2015-06-18T20:04:33Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@bdunbar](https://discuss.elastic.co/u/bdunbar)
#### Post date: [June 18, 2015, 8:04pm UTC](https://discuss.elastic.co/t/es-fell-down-and-it-cant-get-up/23940/1 "2015-06-18T20:04:33Z")
New ES admin. Setup my server. Shoved some data into it. Installed Shield. Uninstalled Shield. Restarted elasticsearch and that fails and poops into the log ..
```
Primary shard is not active or isn't assigned is a known node
```
and
```
Can't recovery from node [node details] with [indices.recovery.compress : true] due to compression bugs - see issue #7210 for details
```
I don't care a _lot_ about the data - I can read it back in from log files. I _do_ care about what happened and how to fix it.
Thoughts?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [June 18, 2015, 10:04pm UTC](https://discuss.elastic.co/t/es-fell-down-and-it-cant-get-up/23940/2 "2015-06-18T22:04:26Z")
Take a look at [https://github.com/elastic/elasticsearch/pull/7210](https://github.com/elastic/elasticsearch/pull/7210) and see if that helps.
Otherwise if you just want to start fresh, `curl -X DELETE localhost:9200/*` will remove all your indices and you can ingest things again.
---
### Author:  [@bdunbar](https://discuss.elastic.co/u/bdunbar)
#### Post date: [June 18, 2015, 10:13pm UTC](https://discuss.elastic.co/t/es-fell-down-and-it-cant-get-up/23940/3 "2015-06-18T22:13:18Z")
Thanks - I'm leaning to the 'start over again' option.
---
### Author:  [@bdunbar](https://discuss.elastic.co/u/bdunbar)
#### Post date: [June 18, 2015, 10:22pm UTC](https://discuss.elastic.co/t/es-fell-down-and-it-cant-get-up/23940/4 "2015-06-18T22:22:09Z")
> [@warkolm](#):
>
> Take a look at [https://github.com/elastic/elasticsearch/pull/7210](https://github.com/elastic/elasticsearch/pull/7210) and see if that helps.
> The problem is old nodes with this setting enabled would use the old buggy code, which can then cause data copied between and old and new node to become corrupted.
Ah. I had installed 1.4 (following an guide published last year by Digital Ocean) then upgraded to 1.6. Guessing d the install/uninstall of shield triggered the problem in 1710?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:06am UTC](https://discuss.elastic.co/t/es-fell-down-and-it-cant-get-up/23940/5 "2017-07-06T00:06:36Z")