# Elastic search fails after some time **URL:** \ **Category:** Elasticsearch\ **Created:** [January 24, 2016, 6:10am UTC](https://discuss.elastic.co/t/elastic-search-fails-after-some-time/39965 "2016-01-24T06:10:07Z")\ **Posts on this page:** 7\ **Page:** 2
**Author:** ![ambarishrh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ambarishrh/32/7348_2.png) [@ambarishrh](https://discuss.elastic.co/u/ambarishrh)\ **Post date:** [January 31, 2016, 7:58pm UTC](https://discuss.elastic.co/t/elastic-search-fails-after-some-time/39965/21 "2016-01-31T19:58:06Z")
Sorted that too, it was a local firewall issue. Thank all. Now need to monitor ES for some time to make sure it doesnt fail! ---
**Author:** ![trsteel88](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/trsteel88/32/8709_2.png) [@trsteel88](https://discuss.elastic.co/u/trsteel88)\ **Post date:** [April 7, 2016, 7:52am UTC](https://discuss.elastic.co/t/elastic-search-fails-after-some-time/39965/22 "2016-04-07T07:52:43Z")
I am having this same problem. Was a solution found for this? Elasticsearch crashes after a short amount of time is restarts. Nothing in the elasticsearch log. The error is similar to OP's # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fb11a9f67c4, pid=976388, tid=140396317169408 # # JRE version: OpenJDK Runtime Environment (8.0\_71-b15) (build 1.8.0\_71-b15) # Java VM: OpenJDK 64-Bit Server VM (25.71-b15 mixed mode linux-amd64 compressed oops) # Problematic frame: # V [libjvm.so+0x5387c4] # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # If you would like to submit a bug report, please visit: # [http://bugreport.java.com/bugreport/crash.jsp](http://bugreport.java.com/bugreport/crash.jsp) # --------------- T H R E A D --------------- Current thread (0x00007fafd400a800): JavaThread "elasticsearch[Anti-Cap][management][T#1]" daemon [\_thread\_in\_vm, id=976482, stack(0x00007fb0908cd000,0x00007fb0909ce000)] siginfo: si\_signo: 11 (SIGSEGV), si\_code: 128 (SI\_KERNEL), si\_addr: 0x0000000000000000 ---
**Author:** ![polyfractal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polyfractal/32/48162_2.png) [@polyfractal](https://discuss.elastic.co/u/polyfractal)\ **Post date:** [April 7, 2016, 3:03pm UTC](https://discuss.elastic.co/t/elastic-search-fails-after-some-time/39965/23 "2016-04-07T15:03:59Z")
> [@trsteel88](#): > > I am having this same problem. Was a solution found for this? What version of ES are you on? If it's 1.x, it may be from our usage of Sigar (used to collect host stats/metrics). Iirc there have been problems with Sigar throwing segfaults in the past. We removed Sigar in 2.x. So if you're on 2.0+, the problem is likely just a bug in the JVM and I'm not really sure we can help much. I'm not aware of any outstanding bugs that affect ES on u71, but perhaps there is a new one you've run into. I'd file a bug report at Oracle/OpenJDK with as much reproduction details as you can. Are you using G1 GC? If yes, can you switch back to CMS and see if the problem continues? G1 is still ... dicey. For example, bugs like this still exist: [Loading...](https://bugs.openjdk.java.net/browse/JDK-8148175) , so who knows what kind of problems it causes 🙂 ---
**Author:** ![trsteel88](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/trsteel88/32/8709_2.png) [@trsteel88](https://discuss.elastic.co/u/trsteel88)\ **Post date:** [April 9, 2016, 1:31am UTC](https://discuss.elastic.co/t/elastic-search-fails-after-some-time/39965/24 "2016-04-09T01:31:37Z")
Upgrading Java to 1.8 (from 1.7) and setting ulimit-c unlimited seems to have fixed the problem. FYI, I am running ES 1.7.5 ---
**Author:** ![cars10](https://avatars.discourse-cdn.com/v4/letter/c/839c29/32.png) [@cars10](https://discuss.elastic.co/u/cars10)\ **Post date:** [May 4, 2017, 6:33am UTC](https://discuss.elastic.co/t/elastic-search-fails-after-some-time/39965/25 "2017-05-04T06:33:02Z")
I experience the same issue. Sometimes elasticsearch just stopps, but sadly the daemon does not - so it does not automatically restart. System: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial ``` Elasticsearch: ``` $ curl localhost:9200 { "name" : "xcRongv", "cluster_name" : "elasticsearch", "cluster_uuid" : "_vh8wSYVQt2tNPlzQJYjVA", "version" : { "number" : "5.3.2", "build_hash" : "3068195", "build_date" : "2017-04-24T16:15:59.481Z", "build_snapshot" : false, "lucene_version" : "6.4.2" }, "tagline" : "You Know, for Search" } ``` Java: ``` $ java -version openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode) ``` The error is similiar to the other errors mentioned here. Syslog only mentions: ``` systemd[1]: elasticsearch.service: Main process exited, code=killed, status=6/ABRT ``` And in /tmp/hs\_err\_pid1110.log ``` # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f931557e371, pid=1110, tid=0x00007f93001d9700 # # JRE version: OpenJDK Runtime Environment (8.0_121-b13) (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13) # Java VM: OpenJDK 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops) # Problematic frame: # V [libjvm.so+0x624371] # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # ... followed by a long dump. ``` complete error: [https://pastebin.com/G3Ct0jY9](https://pastebin.com/G3Ct0jY9) ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 4, 2017, 8:50am UTC](https://discuss.elastic.co/t/elastic-search-fails-after-some-time/39965/26 "2017-05-04T08:50:10Z")
This thread is over a year old, please start a new one 🙂 ---
**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, 10:00pm UTC](https://discuss.elastic.co/t/elastic-search-fails-after-some-time/39965/27 "2017-07-05T22:00:37Z")
[Previous page](https://discuss.elastic.co/t/elastic-search-fails-after-some-time/39965.md?page=1)