# Server didn't recover from too many open files error

**URL:** <https://discuss.elastic.co/t/server-didnt-recover-from-too-many-open-files-error/8640>\
**Category:** Elasticsearch\
**Created:** [August 5, 2012, 9:46pm UTC](https://discuss.elastic.co/t/server-didnt-recover-from-too-many-open-files-error/8640 "2012-08-05T21:46:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pavel\_Dvorak](https://avatars.discourse-cdn.com/v4/letter/p/b9e5f3/32.png) [@Pavel\_Dvorak](https://discuss.elastic.co/u/Pavel_Dvorak)\
**Post date:** [August 5, 2012, 9:46pm UTC](https://discuss.elastic.co/t/server-didnt-recover-from-too-many-open-files-error/8640/1 "2012-08-05T21:46:03Z")

</div>

I didn't have unlimited files option enabled. ES worked fine for few months  
and today it crashed. Had 0.19.2.  
IndexFailedEngineException occured with Too many open files  
I tried to restart ES but i didn't shutdown, so I killed it. But didn't  
start again...  
Had to restore from backup  
Attaching full log  
Note: failed to obtain node lock error is due wrong file permission after  
restoring from backup  
thanks for help

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [August 7, 2012, 9:51pm UTC](https://discuss.elastic.co/t/server-didnt-recover-from-too-many-open-files-error/8640/2 "2012-08-07T21:51:58Z")

</div>

I don't see the problem in the log, seems like ti started properly, maybe I am missing something? As a side note, things has improved even more in recent versions.

On Aug 5, 2012, at 11:46 PM, Pavel Dvorak [pavel.dvorak.work@gmail.com](mailto:pavel.dvorak.work@gmail.com) wrote:

> I didn't have unlimited files option enabled. ES worked fine for few months and today it crashed. Had 0.19.2.  
> IndexFailedEngineException occured with Too many open files  
> I tried to restart ES but i didn't shutdown, so I killed it. But didn't start again...  
> Had to restore from backup  
> Attaching full log  
> Note: failed to obtain node lock error is due wrong file permission after restoring from backup  
> thanks for help  
> \<elasticsearch.zip\>

---

<div class="post-metadata">

**Author:** ![Pavel\_Dvorak](https://avatars.discourse-cdn.com/v4/letter/p/b9e5f3/32.png) [@Pavel\_Dvorak](https://discuss.elastic.co/u/Pavel_Dvorak)\
**Post date:** [August 7, 2012, 10:05pm UTC](https://discuss.elastic.co/t/server-didnt-recover-from-too-many-open-files-error/8640/3 "2012-08-07T22:05:35Z")

</div>

I have updated now  
the last part of the log is after restore  
try to find this line  
org.elasticsearch.index.IndexShardMissingException: [action\_log\_console][1]  
missing  
it didn't work after this, it displayed red status

Dne úterý, 7. srpna 2012 23:51:58 UTC+2 kimchy napsal(a):

> I don't see the problem in the log, seems like ti started properly, maybe  
> I am missing something? As a side note, things has improved even more in  
> recent versions.
> 
> On Aug 5, 2012, at 11:46 PM, Pavel Dvorak \<[pavel.dv...@gmail.com](mailto:pavel.dv...@gmail.com)\<javascript:\>\>  
> wrote:
> 
> > I didn't have unlimited files option enabled. ES worked fine for few  
> > months and today it crashed. Had 0.19.2.  
> > IndexFailedEngineException occured with Too many open files  
> > I tried to restart ES but i didn't shutdown, so I killed it. But didn't  
> > start again...  
> > Had to restore from backup  
> > Attaching full log  
> > Note: failed to obtain node lock error is due wrong file permission  
> > after restoring from backup  
> > thanks for help  
> > \<elasticsearch.zip\>

---

<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 6, 2017, 3:17am UTC](https://discuss.elastic.co/t/server-didnt-recover-from-too-many-open-files-error/8640/4 "2017-07-06T03:17:25Z")

</div>

Closed on July 6, 2017, 3:17am UTC


