### Author:  [@billy6](https://discuss.elastic.co/u/billy6)
#### Post date: [May 11, 2017, 9:33am UTC](https://discuss.elastic.co/t/elasticsearch-index-not-loaded-es-curator/85357/1 "2017-05-11T09:33:22Z")
HEllo Everybody,
My elasticsearch instance was not working this morning. It was because the device was without any more space.
I have realized I was having a problem with ES curator.
```
python /usr/lib/python2.6/site-packages/curator/curator.py --host 127.0.0.1 delete indices --older-than 30 --time-unit days --timestring '%Y.%m.%d'
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/curator/curator.py", line 2, in
from .cli import cli
ValueError: Attempted relative import in non-package
```
Do you have any idea why this could be happening?
Besides, I can not load the last index, any idea about how to solve it?
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [May 11, 2017, 1:21pm UTC](https://discuss.elastic.co/t/elasticsearch-index-not-loaded-es-curator/85357/2 "2017-05-11T13:21:01Z")
Well, I would first off point out that you're using a _very_ old version of Curator. 3.x is no longer supported.
Second, I would point out that you're launching Curator incorrectly. It should be launched by the `entry_point`, which is usually `/usr/bin/curator` or `/usr/local/bin/curator`.
What version of Elasticsearch are you using?
---
### Author:  [@billy6](https://discuss.elastic.co/u/billy6)
#### Post date: [May 12, 2017, 8:44am UTC](https://discuss.elastic.co/t/elasticsearch-index-not-loaded-es-curator/85357/3 "2017-05-12T08:44:56Z")
Thank you for your quick response Aaron @theuntergeek
This is the configuration I am using now:
Curator version 3.3.0
Python 2.6
Elasticsearch version 1.7.1
It was working perfectly fine before, but now suddenly stopped.
What is your advice?
And any idea about how to restore the index ? it seems to be corrupted.
Thanks
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [May 12, 2017, 4:30pm UTC](https://discuss.elastic.co/t/elasticsearch-index-not-loaded-es-curator/85357/4 "2017-05-12T16:30:36Z")
I can't tell you if there's a corrupted snapshot or not. The error above indicates something happened to your python instance and it doesn't like how you're launching Curator.
You should at least be using 3.5.1, and launch using the `entry_point`, not from launching `python /path/to/wherever/curator.py/is`, which was never a recommended thing. If that was not working, the likely issue and fix were both described [in this FAQ](https://www.elastic.co/guide/en/elasticsearch/client/curator/3.5/entrypoint-fix.html) in the official documentation.
---
### Author:  [@billy6](https://discuss.elastic.co/u/billy6)
#### Post date: [May 23, 2017, 10:10am UTC](https://discuss.elastic.co/t/elasticsearch-index-not-loaded-es-curator/85357/5 "2017-05-23T10:10:25Z")
Thank you,
It was a problem with urllib3.
I reinstalled it and it was solved.
Do we have any idea about what to do with the indices that are in that state?
size:unknown
docs: unknown
Now I have them closed but I woul like to get it back
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [May 23, 2017, 5:57pm UTC](https://discuss.elastic.co/t/elasticsearch-index-not-loaded-es-curator/85357/6 "2017-05-23T17:57:26Z")
With no logs, I cannot even tell what the issue is.
I can tell you that Elasticsearch cannot report on the size or number of documents in a closed index. A number of these and similar caveats are described [in the Curator documentation for deleting by space](https://www.elastic.co/guide/en/elasticsearch/client/curator/5.0/filtertype_space.html#_deleting_indices_by_space).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 20, 2017, 6:10pm UTC](https://discuss.elastic.co/t/elasticsearch-index-not-loaded-es-curator/85357/7 "2017-06-20T18:10:54Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.