# ES-5.2.1 server is continuously getting dead
**URL:** https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695
**Category:** Elasticsearch
**Created:** [February 20, 2017, 9:22am UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695 "2017-02-20T09:22:25Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@Yashpal\_Singh](https://discuss.elastic.co/u/Yashpal_Singh)
#### Post date: [February 20, 2017, 9:22am UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/1 "2017-02-20T09:22:25Z")
**LOGS**
[2017-02-20T08:55:20,322][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [abc] fatal error in thread [elasticsearch[abc][search][T#7]], exiting
**java.lang.StackOverflowError: null**
at org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1309) ~[lucene-core-6.4.1.jar:6.4.1 72f75b2503fa0aa4f0aff76d439874feb923bb0e - jpountz - 2017-02-01 14:43:32]
at org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1309) ~[lucene-core-6.4.1.jar:6.4.1 72f75b2503fa0aa4f0aff76d439874feb923bb0e - jpountz - 2017-02-01 14:43:32]
at org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1309) ~[lucene-core-6.4.1.jar:6.4.1 72f75b2503fa0aa4f0aff76d439874feb923bb0e - jpountz - 2017-02-01 14:43:32]
Could you please let me know, What exaclty is the isssue here.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 20, 2017, 9:42pm UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/2 "2017-02-20T21:42:41Z")
What OS? What JVM?
---
### Author:  [@Andrey\_Plotkin](https://discuss.elastic.co/u/Andrey_Plotkin)
#### Post date: [February 25, 2017, 12:09pm UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/3 "2017-02-25T12:09:49Z")
I may confirm the issue for version[5.2.0]:
[2017-02-25T12:22:12,274][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [Node2] fatal error in thread [elasticsearch[Node2][search][T#11]], exiting
java.lang.StackOverflowError: null
at org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1309) ~[lucene-core-6.4.0.jar:6.4.0 bbe4b08cc1fb673d0c3eb4b8455f23ddc1364124 - jim - 2017-01-17 15:57:29]
at org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1309) ~[lucene-core-6.4.0.jar:6.4.0 bbe4b08cc1fb673d0c3eb4b8455f23ddc1364124 - jim - 2017-01-17 15:57:29]
at org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1309) ~[lucene-core-6.4.0.jar:6.4.0 bbe4b08cc1fb673d0c3eb4b8455f23ddc1364124 - jim - 2017-01-17 15:57:29]
at org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1309) ~[lucene-core-6.4.0.jar:6.4.0 bbe4b08cc1fb673d0c3eb4b8455f23ddc1364124 - jim - 2017-01-17 15:57:29]
at org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1309) ~[lucene-core-6.4.0.jar:6.4.0 bbe4b08cc1fb673d0c3eb4b8455f23ddc1364124 - jim - 2017-01-17 15:57:29]
root@n1 ~ # uname -v
#1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02)
root@n1 ~ # lsb\_release -da
Distributor ID: Debian
Description: Debian GNU/Linux 8.5 (jessie)
Release: 8.5
Codename: jessie
root@n1 / # java -version
openjdk version "1.8.0\_121"
OpenJDK Runtime Environment (build 1.8.0\_121-8u121-b13-1~bpo8+1-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 25, 2017, 10:03pm UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/4 "2017-02-25T22:03:54Z")
Can you share the entire log, things before and after this as well.
---
### Author:  [@Andrey\_Plotkin](https://discuss.elastic.co/u/Andrey_Plotkin)
#### Post date: [February 26, 2017, 8:56am UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/5 "2017-02-26T08:56:32Z")
[Log file](https://dl.dropboxusercontent.com/u/30981762/log.txt)
Here is the log file.
As you may see, lines before the SOE seem ordinary, nothing special happens.
The last line is 1.5 hours later, when I started the node.
---
### Author:  [@Andrey\_Plotkin](https://discuss.elastic.co/u/Andrey_Plotkin)
#### Post date: [February 27, 2017, 4:57am UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/6 "2017-02-27T04:57:52Z")
More info about ES installation:
"version": {
"number": "5.2.0",
"build\_hash": "24e05b9",
"build\_date": "2017-01-24T19:52:35.800Z",
"build\_snapshot": false,
"lucene\_version": "6.4.0"
},
---
### Author:  [@Yashpal\_Singh](https://discuss.elastic.co/u/Yashpal_Singh)
#### Post date: [March 8, 2017, 6:51am UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/7 "2017-03-08T06:51:34Z")
Same issue occured today with the same set of logs
Same issue is also faced by solr guys `http://lucene.472066.n3.nabble.com/StackOverflowError-when-building-suggestions-td4267700.html`
---
### Author:  [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)
#### Post date: [March 8, 2017, 6:58am UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/8 "2017-03-08T06:58:32Z")
I'm having the same problem, for every few days my service is getting dead.
> [@Problem with elasticsearch service](https://discuss.elastic.co/t/problem-with-elasticsearch-service/77541):
>
> I have upgraded our cluster to 5.1.2. After the upgrade we are getting frequent problem with elasticsearch. For every 3-4 days elasticsearch is dying with fowllowing error. [root@ushapld001211a ~]# service elasticsearch status elasticsearch dead but pid file exists We have enough space. we are restarting the service and its becoming normal. Its happening for every 3-4 days .Please provide me a solution what i need to check. @warkolm please help me
---
### Author:  [@Yashpal\_Singh](https://discuss.elastic.co/u/Yashpal_Singh)
#### Post date: [March 8, 2017, 7:00am UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/9 "2017-03-08T07:00:43Z")
@Akhilesh_Anb Please share the cluster logs and settings
---
### Author:  [@Yashpal\_Singh](https://discuss.elastic.co/u/Yashpal_Singh)
#### Post date: [March 8, 2017, 7:05am UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/10 "2017-03-08T07:05:02Z")
java -version
openjdk version "1.8.0\_121"
OpenJDK Runtime Environment (build 1.8.0\_121-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)
NAME="Amazon Linux AMI"
VERSION="2016.09"
ID="amzn"
ID\_LIKE="rhel fedora"
VERSION\_ID="2016.09"
Amazon Linux AMI release 2016.09
---
### Author:  [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)
#### Post date: [March 8, 2017, 7:24am UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/11 "2017-03-08T07:24:41Z")
Here is the link of [log file](https://www.dropbox.com/s/y4m047g635qfwvo/log%20file.log?dl=0)
> java version "1.8.0\_102"
> Java(TM) SE Runtime Environment (build 1.8.0\_102-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
Os :- Centos 64 bit
Elasticsearch - 5.1.2
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 5, 2017, 7:24am UTC](https://discuss.elastic.co/t/es-5-2-1-server-is-continuously-getting-dead/75695/12 "2017-04-05T07:24:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.