# Elasticsearch server terminates itself **URL:** \ **Category:** Elasticsearch\ **Created:** [June 1, 2012, 8:21pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945 "2012-06-01T20:21:43Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 1, 2012, 8:21pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/1 "2012-06-01T20:21:43Z")
Hi, Does anyone know why ES terminates itself after indexing x number of documents? I restarted it 3 times today. This is how I start the server. Not passing any arguments. > ./elasticsearch Thanks, Kara ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 1, 2012, 8:54pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/2 "2012-06-01T20:54:40Z")
Anything in logs ? David 😉 Twitter : @dadoonet / @elasticsearchfr Le 1 juin 2012 à 22:21, Kara [karine.marabyan@aero.org](mailto:karine.marabyan@aero.org) a écrit : > Hi, > > Does anyone know why ES terminates itself after indexing x number of > documents? I restarted it 3 times today. > > This is how I start the server. Not passing any arguments. > > > ./elasticsearch > > Thanks, > Kara ---
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 1, 2012, 9:32pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/3 "2012-06-01T21:32:46Z")
Nope. Also, this is elasticsearch-0.19.2 with mongodb river plugin. There was "Segmentation Fault" on the terminal where ES was running. Thanks, Kara On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > Hi, > > Does anyone know why ES terminates itself after indexing x number of > documents? I restarted it 3 times today. > > This is how I start the server. Not passing any arguments. > > > ./elasticsearch > > Thanks, > Kara ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 1, 2012, 10:50pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/4 "2012-06-01T22:50:09Z")
What is your jvm ? ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? David Le 1 juin 2012 à 23:32, Kara [karine.marabyan@aero.org](mailto:karine.marabyan@aero.org) a écrit : > Nope. > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > was "Segmentation Fault" on the terminal where ES was running. > > Thanks, > Kara > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > Hi, > > > > Does anyone know why ES terminates itself after indexing x number of > > documents? I restarted it 3 times today. > > > > This is how I start the server. Not passing any arguments. > > > > > ./elasticsearch > > > > Thanks, > > Kara ---
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 1, 2012, 11:15pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/5 "2012-06-01T23:15:26Z")
java version "1.6.0\_31" Ok - I will download 0.19.4 now. Thanks, Kara On Jun 1, 3:50 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > What is your jvm ? > ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? > > David > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > Nope. > > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > > was "Segmentation Fault" on the terminal where ES was running. > > > Thanks, > > Kara > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > Hi, > > > > Does anyone know why ES terminates itself after indexing x number of > > > documents? I restarted it 3 times today. > > > > This is how I start the server. Not passing any arguments. > > > > > ./elasticsearch > > > > Thanks, > > > Kara ---
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 2, 2012, 3:49pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/6 "2012-06-02T15:49:56Z")
It terminated in the new version too. No error messages in the log file. thanks for your help! Kara On Jun 1, 4:15 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > java version "1.6.0\_31" > > Ok - I will download 0.19.4 now. > > Thanks, > Kara > On Jun 1, 3:50 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > What is your jvm ? > > ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? > > > David > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > Nope. > > > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > > > was "Segmentation Fault" on the terminal where ES was running. > > > > Thanks, > > > Kara > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > Hi, > > > > > Does anyone know why ES terminates itself after indexing x number of > > > > documents? I restarted it 3 times today. > > > > > This is how I start the server. Not passing any arguments. > > > > > > ./elasticsearch > > > > > Thanks, > > > > Kara- Hide quoted text - > > - Show quoted text - ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [June 3, 2012, 3:33pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/7 "2012-06-03T15:33:41Z")
A two-month old release is already old? 🙂 On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > What is your jvm ? > ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? > > David > > Le 1 juin 2012 à 23:32, Kara [karine.marabyan@aero.org](mailto:karine.marabyan@aero.org) a écrit : > > > Nope. > > > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > > was "Segmentation Fault" on the terminal where ES was running. > > > > Thanks, > > Kara > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > Hi, > > > > > > Does anyone know why ES terminates itself after indexing x number of > > > documents? I restarted it 3 times today. > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > ./elasticsearch > > > > > > Thanks, > > > Kara ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 3, 2012, 4:28pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/8 "2012-06-03T16:28:07Z")
Lol Ivan ! Not old, but updates exists 😉 BTW, Karine, are you running on Linux, windows, Mac ? Do you use OpenJDK ? Did you modify something in config files (memory settings ?) David Le 3 juin 2012 à 17:33, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) a écrit : > A two-month old release is already old? 🙂 > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > > > What is your jvm ? > > ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? > > > > David > > > > Le 1 juin 2012 à 23:32, Kara [karine.marabyan@aero.org](mailto:karine.marabyan@aero.org) a écrit : > > > > > Nope. > > > > > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > > > was "Segmentation Fault" on the terminal where ES was running. > > > > > > Thanks, > > > Kara > > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > Hi, > > > > > > > > Does anyone know why ES terminates itself after indexing x number of > > > > documents? I restarted it 3 times today. > > > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > > > ./elasticsearch > > > > > > > > Thanks, > > > > Kara ---
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 4, 2012, 3:19pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/9 "2012-06-04T15:19:44Z")
I am running Scientific Linux release 6.2 (Carbon). And it's a Openstack virtual instance. > Do you use OpenJDK ? > Yes - it is OpenJDK. > Did you modify something in config files (memory settings ?) > No - didn't change any configuration parameters. I am running the > defaults. Thanks so much for your help! Karine On Jun 3, 9:28 am, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > Lol Ivan ! > Not old, but updates exists 😉 > > BTW, Karine, are you running on Linux, windows, Mac ? > Do you use OpenJDK ? > > Did you modify something in config files (memory settings ?) > > David > > Le 3 juin 2012 à 17:33, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) a écrit : > > > A two-month old release is already old? 🙂 > > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > What is your jvm ? > > > ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? > > > > David > > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > Nope. > > > > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > > > > was "Segmentation Fault" on the terminal where ES was running. > > > > > Thanks, > > > > Kara > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > Hi, > > > > > > Does anyone know why ES terminates itself after indexing x number of > > > > > documents? I restarted it 3 times today. > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > ./elasticsearch > > > > > > Thanks, > > > > > Kara ---
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 4, 2012, 6:32pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/10 "2012-06-04T18:32:55Z")
Hi David, I installed the ES on the physical box that runs centos and also oracle jdk 1.6. It terminated in 1 hour and 15 minutes again. That's about how much time it takes to terminate itself for all my tries. I got this error this time: Sorry I had to block the ip addresses in the logs. [2012-06-04 10:04:10,633][INFO][river.mongodb] [Wilson, Sam] [mongodb][mongodb] No known previous slurping time for this collection [2012-06-04 10:04:11,016][INFO][cluster.metadata] [Wilson, Sam] [\_river] update\_mapping [mongodb] (dynamic) [2012-06-04 11:16:37,278][WARN][discovery.zen.ping.multicast] [Wilson, Sam] failed to read requesting data from /some ip address here:54328 org.elasticsearch.ElasticSearchIllegalStateException: failed multicast message, probably message from previous version at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing $Receiver.run(MulticastZenPing.java:406) at java.lang.Thread.run(Thread.java:662) [2012-06-04 11:16:38,777][WARN][discovery.zen.ping.multicast] [Wilson, Sam] failed to read requesting data from /some ip address here:54328 org.elasticsearch.ElasticSearchIllegalStateException: failed multicast message, probably message from previous version at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing $Receiver.run(MulticastZenPing.java:406) at java.lang.Thread.run(Thread.java:662) On Jun 4, 8:19 am, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > I am running Scientific Linux release 6.2 (Carbon). And it's a > Openstack virtual instance. > > > Do you use OpenJDK ? > > Yes - it is OpenJDK. > > > Did you modify something in config files (memory settings ?) > > No - didn't change any configuration parameters. I am running the > defaults. > > Thanks so much for your help! > Karine > > On Jun 3, 9:28 am, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > Lol Ivan ! > > Not old, but updates exists 😉 > > > BTW, Karine, are you running on Linux, windows, Mac ? > > Do you use OpenJDK ? > > > Did you modify something in config files (memory settings ?) > > > David > > > Le 3 juin 2012 à 17:33, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) a écrit : > > > > A two-month old release is already old? 🙂 > > > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > What is your jvm ? > > > > ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? > > > > > David > > > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > > Nope. > > > > > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > > > > > was "Segmentation Fault" on the terminal where ES was running. > > > > > > Thanks, > > > > > Kara > > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > Hi, > > > > > > > Does anyone know why ES terminates itself after indexing x number of > > > > > > documents? I restarted it 3 times today. > > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > > ./elasticsearch > > > > > > > Thanks, > > > > > > Kara ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 4, 2012, 7:09pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/11 "2012-06-04T19:09:55Z")
Fine. Do you mean that the Elasticsearch process stop after 1 hour ? Or, is it the river that hang after a while ? And you still able to get [http://localhost:9200/](http://localhost:9200/) ? I'm asking that because I got about the same issue with the couchDb river some weeks ago. If ES is killed, I think that there's perhaps something wrong in the mongodb river (memory usage ?). I did not look at the source code. Is someone else on the list is using this river in production ? David Le 4 juin 2012 à 20:32, Kara [karine.marabyan@aero.org](mailto:karine.marabyan@aero.org) a écrit : > Hi David, > > I installed the ES on the physical box that runs centos and also > oracle jdk 1.6. It terminated in 1 hour and 15 minutes again. That's > about how much time it takes to terminate itself for all my tries. I > got this error this time: Sorry I had to block the ip addresses in the > logs. > > [2012-06-04 10:04:10,633][INFO][river.mongodb] [Wilson, > Sam] [mongodb][mongodb] No known previous slurping time for this > collection > [2012-06-04 10:04:11,016][INFO][cluster.metadata] [Wilson, > Sam] [\_river] update\_mapping [mongodb] (dynamic) > [2012-06-04 11:16:37,278][WARN][discovery.zen.ping.multicast] > [Wilson, Sam] failed to read requesting data from /some ip address > here:54328 > org.elasticsearch.ElasticSearchIllegalStateException: failed multicast > message, probably message from previous version > at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > $Receiver.run(MulticastZenPing.java:406) > at java.lang.Thread.run(Thread.java:662) > [2012-06-04 11:16:38,777][WARN][discovery.zen.ping.multicast] > [Wilson, Sam] failed to read requesting data from /some ip address > here:54328 > org.elasticsearch.ElasticSearchIllegalStateException: failed multicast > message, probably message from previous version > at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > $Receiver.run(MulticastZenPing.java:406) > at java.lang.Thread.run(Thread.java:662) > > On Jun 4, 8:19 am, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > I am running Scientific Linux release 6.2 (Carbon). And it's a > > Openstack virtual instance. > > > > > Do you use OpenJDK ? > > > > Yes - it is OpenJDK. > > > > > Did you modify something in config files (memory settings ?) > > > > No - didn't change any configuration parameters. I am running the > > defaults. > > > > Thanks so much for your help! > > Karine > > > > On Jun 3, 9:28 am, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > Lol Ivan ! > > > Not old, but updates exists 😉 > > > > > BTW, Karine, are you running on Linux, windows, Mac ? > > > Do you use OpenJDK ? > > > > > Did you modify something in config files (memory settings ?) > > > > > David > > > > > Le 3 juin 2012 à 17:33, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) a écrit : > > > > > > A two-month old release is already old? 🙂 > > > > > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > What is your jvm ? > > > > > ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? > > > > > > > David > > > > > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > > > > Nope. > > > > > > > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > > > > > > was "Segmentation Fault" on the terminal where ES was running. > > > > > > > > Thanks, > > > > > > Kara > > > > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > Does anyone know why ES terminates itself after indexing x number of > > > > > > > documents? I restarted it 3 times today. > > > > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > > > > ./elasticsearch > > > > > > > > > Thanks, > > > > > > > Kara ---
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 4, 2012, 7:26pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/12 "2012-06-04T19:26:49Z")
I just do the following: > ps -ef | grep elast $ ps -ef | grep elas dib 29863 1 0 11:21 pts/4 00:00:11 /opt/dsw/java/bin/java -Xms256m -Xmx1g -Xss256k -XX:+UseParNewGC -XX:+UseConcMarkSweepGC - XX:CMSInitiatingOccupancyFraction=75 -XX: +UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError - Delasticsearch -Des.path.home=/home/dib/elasticsearch-0.19.4 -cp 😕 home/dib/elasticsearch-0.19.4/lib/_:/home/dib/elasticsearch-0.19.4/lib/ sigar/_ org.elasticsearch.bootstrap.Elasticsearch I get no results from the "ps -ef | grep elas" when failed and the curl client doesn't work either. So, no elastic process running at that time. I thought the ES and river are one process. Mongodb servers are fine - just the ES terminates in 1 hour and about 15 minutes. How can I check if it's the mongodb river memory usage? > Is someone else on the list is using this river in production ? > I don't know. Also, how can I collect more logs? I am hoping to see more in the log file when it terminates. Thanks David! Karine On Jun 4, 12:09 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > Fine. Do you mean that the Elasticsearch process stop after 1 hour ? > Or, is it the river that hang after a while ? And you still able to gethttp://localhost:9200/? > > I'm asking that because I got about the same issue with the couchDb river some weeks ago. > > If ES is killed, I think that there's perhaps something wrong in the mongodb river (memory usage ?). I did not look at the source code. > > Is someone else on the list is using this river in production ? > > David > > Le 4 juin 2012 à 20:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > Hi David, > > > I installed the ES on the physical box that runs centos and also > > oracle jdk 1.6. It terminated in 1 hour and 15 minutes again. That's > > about how much time it takes to terminate itself for all my tries. I > > got this error this time: Sorry I had to block the ip addresses in the > > logs. > > > [2012-06-04 10:04:10,633][INFO][river.mongodb] [Wilson, > > Sam] [mongodb][mongodb] No known previous slurping time for this > > collection > > [2012-06-04 10:04:11,016][INFO][cluster.metadata] [Wilson, > > Sam] [\_river] update\_mapping [mongodb] (dynamic) > > [2012-06-04 11:16:37,278][WARN][discovery.zen.ping.multicast] > > [Wilson, Sam] failed to read requesting data from /some ip address > > here:54328 > > org.elasticsearch.ElasticSearchIllegalStateException: failed multicast > > message, probably message from previous version > > at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > $Receiver.run(MulticastZenPing.java:406) > > at java.lang.Thread.run(Thread.java:662) > > [2012-06-04 11:16:38,777][WARN][discovery.zen.ping.multicast] > > [Wilson, Sam] failed to read requesting data from /some ip address > > here:54328 > > org.elasticsearch.ElasticSearchIllegalStateException: failed multicast > > message, probably message from previous version > > at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > $Receiver.run(MulticastZenPing.java:406) > > at java.lang.Thread.run(Thread.java:662) > > > On Jun 4, 8:19 am, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > I am running Scientific Linux release 6.2 (Carbon). And it's a > > > Openstack virtual instance. > > > > > Do you use OpenJDK ? > > > > Yes - it is OpenJDK. > > > > > Did you modify something in config files (memory settings ?) > > > > No - didn't change any configuration parameters. I am running the > > > defaults. > > > > Thanks so much for your help! > > > Karine > > > > On Jun 3, 9:28 am, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > Lol Ivan ! > > > > Not old, but updates exists 😉 > > > > > BTW, Karine, are you running on Linux, windows, Mac ? > > > > Do you use OpenJDK ? > > > > > Did you modify something in config files (memory settings ?) > > > > > David > > > > > Le 3 juin 2012 à 17:33, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) a écrit : > > > > > > A two-month old release is already old? 🙂 > > > > > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > > > What is your jvm ? > > > > > > ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? > > > > > > > David > > > > > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > > > > Nope. > > > > > > > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > > > > > > > was "Segmentation Fault" on the terminal where ES was running. > > > > > > > > Thanks, > > > > > > > Kara > > > > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > > > Hi, > > > > > > > > > Does anyone know why ES terminates itself after indexing x number of > > > > > > > > documents? I restarted it 3 times today. > > > > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > > > > ./elasticsearch > > > > > > > > > Thanks, > > > > > > > > Kara ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 4, 2012, 7:39pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/13 "2012-06-04T19:39:37Z")
Hum... Sounds bad. You can set logs to trace. See config/logging.yml file. I think that a new Line like following will work: river.mongodb: TRACE BTW do you see a hprof file or something like that in your es dir ? Le 4 juin 2012 à 21:26, Kara [karine.marabyan@aero.org](mailto:karine.marabyan@aero.org) a écrit : > I just do the following: > > > ps -ef | grep elast > > $ ps -ef | grep elas > dib 29863 1 0 11:21 pts/4 00:00:11 /opt/dsw/java/bin/java > -Xms256m -Xmx1g -Xss256k -XX:+UseParNewGC -XX:+UseConcMarkSweepGC - > XX:CMSInitiatingOccupancyFraction=75 -XX: > +UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError - > Delasticsearch -Des.path.home=/home/dib/elasticsearch-0.19.4 -cp 😕 > home/dib/elasticsearch-0.19.4/lib/_:/home/dib/elasticsearch-0.19.4/lib/ > sigar/_ org.elasticsearch.bootstrap.Elasticsearch > > I get no results from the "ps -ef | grep elas" when failed and the > curl client doesn't work either. So, no elastic process running at > that time. > > I thought the ES and river are one process. Mongodb servers are fine - > just the ES terminates in 1 hour and about 15 minutes. > > How can I check if it's the mongodb river memory usage? > > > Is someone else on the list is using this river in production ? > > I don't know. > > Also, how can I collect more logs? I am hoping to see more in the log > file when it terminates. > > Thanks David! > Karine > On Jun 4, 12:09 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > Fine. Do you mean that the Elasticsearch process stop after 1 hour ? > > Or, is it the river that hang after a while ? And you still able to gethttp://localhost:9200/? > > > > I'm asking that because I got about the same issue with the couchDb river some weeks ago. > > > > If ES is killed, I think that there's perhaps something wrong in the mongodb river (memory usage ?). I did not look at the source code. > > > > Is someone else on the list is using this river in production ? > > > > David > > > > Le 4 juin 2012 à 20:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > Hi David, > > > > > I installed the ES on the physical box that runs centos and also > > > oracle jdk 1.6. It terminated in 1 hour and 15 minutes again. That's > > > about how much time it takes to terminate itself for all my tries. I > > > got this error this time: Sorry I had to block the ip addresses in the > > > logs. > > > > > [2012-06-04 10:04:10,633][INFO][river.mongodb] [Wilson, > > > Sam] [mongodb][mongodb] No known previous slurping time for this > > > collection > > > [2012-06-04 10:04:11,016][INFO][cluster.metadata] [Wilson, > > > Sam] [\_river] update\_mapping [mongodb] (dynamic) > > > [2012-06-04 11:16:37,278][WARN][discovery.zen.ping.multicast] > > > [Wilson, Sam] failed to read requesting data from /some ip address > > > here:54328 > > > org.elasticsearch.ElasticSearchIllegalStateException: failed multicast > > > message, probably message from previous version > > > at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > $Receiver.run(MulticastZenPing.java:406) > > > at java.lang.Thread.run(Thread.java:662) > > > [2012-06-04 11:16:38,777][WARN][discovery.zen.ping.multicast] > > > [Wilson, Sam] failed to read requesting data from /some ip address > > > here:54328 > > > org.elasticsearch.ElasticSearchIllegalStateException: failed multicast > > > message, probably message from previous version > > > at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > $Receiver.run(MulticastZenPing.java:406) > > > at java.lang.Thread.run(Thread.java:662) > > > > > On Jun 4, 8:19 am, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > I am running Scientific Linux release 6.2 (Carbon). And it's a > > > > Openstack virtual instance. > > > > > > > Do you use OpenJDK ? > > > > > > Yes - it is OpenJDK. > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > No - didn't change any configuration parameters. I am running the > > > > defaults. > > > > > > Thanks so much for your help! > > > > Karine > > > > > > On Jun 3, 9:28 am, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > Lol Ivan ! > > > > > Not old, but updates exists 😉 > > > > > > > BTW, Karine, are you running on Linux, windows, Mac ? > > > > > Do you use OpenJDK ? > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > > David > > > > > > > Le 3 juin 2012 à 17:33, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) a écrit : > > > > > > > > A two-month old release is already old? 🙂 > > > > > > > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > > > > > What is your jvm ? > > > > > > > ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? > > > > > > > > > David > > > > > > > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > > > > > > Nope. > > > > > > > > > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > > > > > > > > was "Segmentation Fault" on the terminal where ES was running. > > > > > > > > > > Thanks, > > > > > > > > Kara > > > > > > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > Does anyone know why ES terminates itself after indexing x number of > > > > > > > > > documents? I restarted it 3 times today. > > > > > > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > > > > > > ./elasticsearch > > > > > > > > > > > Thanks, > > > > > > > > > Kara ---
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 4, 2012, 8:07pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/14 "2012-06-04T20:07:12Z")
No - I didn't find any hprof file in the ES directory. Thanks, Karine On Jun 4, 12:39 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > Hum... Sounds bad. > > You can set logs to trace. See config/logging.yml file. > I think that a new Line like following will work: > river.mongodb: TRACE > > BTW do you see a hprof file or something like that in your es dir ? > > Le 4 juin 2012 à 21:26, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > I just do the following: > > > > > ps -ef | grep elast > > > $ ps -ef | grep elas > > dib 29863 1 0 11:21 pts/4 00:00:11 /opt/dsw/java/bin/java > > -Xms256m -Xmx1g -Xss256k -XX:+UseParNewGC -XX:+UseConcMarkSweepGC - > > XX:CMSInitiatingOccupancyFraction=75 -XX: > > +UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError - > > Delasticsearch -Des.path.home=/home/dib/elasticsearch-0.19.4 -cp 😕 > > home/dib/elasticsearch-0.19.4/lib/_:/home/dib/elasticsearch-0.19.4/lib/ > > sigar/_ org.elasticsearch.bootstrap.Elasticsearch > > > I get no results from the "ps -ef | grep elas" when failed and the > > curl client doesn't work either. So, no elastic process running at > > that time. > > > I thought the ES and river are one process. Mongodb servers are fine - > > just the ES terminates in 1 hour and about 15 minutes. > > > How can I check if it's the mongodb river memory usage? > > > > Is someone else on the list is using this river in production ? > > > I don't know. > > > Also, how can I collect more logs? I am hoping to see more in the log > > file when it terminates. > > > Thanks David! > > Karine > > On Jun 4, 12:09 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > Fine. Do you mean that the Elasticsearch process stop after 1 hour ? > > > Or, is it the river that hang after a while ? And you still able to gethttp://localhost:9200/? > > > > I'm asking that because I got about the same issue with the couchDb river some weeks ago. > > > > If ES is killed, I think that there's perhaps something wrong in the mongodb river (memory usage ?). I did not look at the source code. > > > > Is someone else on the list is using this river in production ? > > > > David > > > > Le 4 juin 2012 à 20:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > Hi David, > > > > > I installed the ES on the physical box that runs centos and also > > > > oracle jdk 1.6. It terminated in 1 hour and 15 minutes again. That's > > > > about how much time it takes to terminate itself for all my tries. I > > > > got this error this time: Sorry I had to block the ip addresses in the > > > > logs. > > > > > [2012-06-04 10:04:10,633][INFO][river.mongodb] [Wilson, > > > > Sam] [mongodb][mongodb] No known previous slurping time for this > > > > collection > > > > [2012-06-04 10:04:11,016][INFO][cluster.metadata] [Wilson, > > > > Sam] [\_river] update\_mapping [mongodb] (dynamic) > > > > [2012-06-04 11:16:37,278][WARN][discovery.zen.ping.multicast] > > > > [Wilson, Sam] failed to read requesting data from /some ip address > > > > here:54328 > > > > org.elasticsearch.ElasticSearchIllegalStateException: failed multicast > > > > message, probably message from previous version > > > > at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > > $Receiver.run(MulticastZenPing.java:406) > > > > at java.lang.Thread.run(Thread.java:662) > > > > [2012-06-04 11:16:38,777][WARN][discovery.zen.ping.multicast] > > > > [Wilson, Sam] failed to read requesting data from /some ip address > > > > here:54328 > > > > org.elasticsearch.ElasticSearchIllegalStateException: failed multicast > > > > message, probably message from previous version > > > > at org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > > $Receiver.run(MulticastZenPing.java:406) > > > > at java.lang.Thread.run(Thread.java:662) > > > > > On Jun 4, 8:19 am, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > I am running Scientific Linux release 6.2 (Carbon). And it's a > > > > > Openstack virtual instance. > > > > > > > Do you use OpenJDK ? > > > > > > Yes - it is OpenJDK. > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > No - didn't change any configuration parameters. I am running the > > > > > defaults. > > > > > > Thanks so much for your help! > > > > > Karine > > > > > > On Jun 3, 9:28 am, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > Lol Ivan ! > > > > > > Not old, but updates exists 😉 > > > > > > > BTW, Karine, are you running on Linux, windows, Mac ? > > > > > > Do you use OpenJDK ? > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > > David > > > > > > > Le 3 juin 2012 à 17:33, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) a écrit : > > > > > > > > A two-month old release is already old? 🙂 > > > > > > > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > > > > > > > What is your jvm ? > > > > > > > > ES 0.19.2 is old. Did you try with a more recent version (0.19.4) ? > > > > > > > > > David > > > > > > > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > > > > > > Nope. > > > > > > > > > > Also, this is elasticsearch-0.19.2 with mongodb river plugin. There > > > > > > > > > was "Segmentation Fault" on the terminal where ES was running. > > > > > > > > > > Thanks, > > > > > > > > > Kara > > > > > > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > Does anyone know why ES terminates itself after indexing x number of > > > > > > > > > > documents? I restarted it 3 times today. > > > > > > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > > > > > > ./elasticsearch > > > > > > > > > > > Thanks, > > > > > > > > > > Kara ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 4, 2012, 8:42pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/15 "2012-06-04T20:42:44Z")
Have you tried to give more memory to your instance ? How many docs are you sending to your ES instance ? David > -----Message d'origine----- > De : [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) > [[mailto:elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)] De la part de Kara > Envoyé : lundi 4 juin 2012 22:07 > À : elasticsearch > Objet : Re: elasticsearch server terminates itself > > No - I didn't find any hprof file in the ES directory. > > Thanks, > Karine > > On Jun 4, 12:39 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > Hum... Sounds bad. > > > > You can set logs to trace. See config/logging.yml file. > > I think that a new Line like following will work: > > river.mongodb: TRACE > > > > BTW do you see a hprof file or something like that in your es dir ? > > > > Le 4 juin 2012 à 21:26, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > I just do the following: > > > > > > > ps -ef | grep elast > > > > > $ ps -ef | grep elas > > > dib 29863 1 0 11:21 pts/4 00:00:11 > > > /opt/dsw/java/bin/java -Xms256m -Xmx1g -Xss256k -XX:+UseParNewGC > > > -XX:+UseConcMarkSweepGC - > > > XX:CMSInitiatingOccupancyFraction=75 -XX: > > > +UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError - > > > Delasticsearch -Des.path.home=/home/dib/elasticsearch-0.19.4 -cp 😕 > > > home/dib/elasticsearch-0.19.4/lib/_:/home/dib/elasticsearch- > > > 0.19.4/l > > > ib/ > > > sigar/_ org.elasticsearch.bootstrap.Elasticsearch > > > > > I get no results from the "ps -ef | grep elas" when failed and the > > > curl client doesn't work either. So, no elastic process running at > > > that time. > > > > > I thought the ES and river are one process. Mongodb servers are > > > fine > > > > > > - just the ES terminates in 1 hour and about 15 minutes. > > > > > How can I check if it's the mongodb river memory usage? > > > > > > Is someone else on the list is using this river in production ? > > > > I don't know. > > > > > Also, how can I collect more logs? I am hoping to see more in the > > > log file when it terminates. > > > > > Thanks David! > > > Karine > > > On Jun 4, 12:09 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > Fine. Do you mean that the Elasticsearch process stop after 1 hour > > > > ? > > > > Or, is it the river that hang after a while ? And you still able > > > > to gethttp://localhost:9200/? > > > > > > I'm asking that because I got about the same issue with the > > > > couchDb river some weeks ago. > > > > > > If ES is killed, I think that there's perhaps something wrong in > > > > the mongodb river (memory usage ?). I did not look at the source code. > > > > > > Is someone else on the list is using this river in production ? > > > > > > David > > > > > > Le 4 juin 2012 à 20:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > > > Hi David, > > > > > > > I installed the ES on the physical box that runs centos and also > > > > > oracle jdk 1.6. It terminated in 1 hour and 15 minutes again. > > > > > That's about how much time it takes to terminate itself for all > > > > > my > > > > > tries. I got this error this time: Sorry I had to block the ip > > > > > addresses in the logs. > > > > > > > [2012-06-04 10:04:10,633][INFO][river.mongodb] > > > > > [Wilson, Sam] [mongodb][mongodb] No known previous slurping time > > > > > for this collection > > > > > [2012-06-04 10:04:11,016][INFO][cluster.metadata] > > > > > [Wilson, Sam] [\_river] update\_mapping [mongodb] (dynamic) > > > > > [2012-06-04 11:16:37,278][WARN][discovery.zen.ping.multicast] > > > > > [Wilson, Sam] failed to read requesting data from /some ip > > > > > address > > > > > here:54328 > > > > > org.elasticsearch.ElasticSearchIllegalStateException: failed > > > > > multicast message, probably message from previous version > > > > > at > > > > > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > > > $Receiver.run(MulticastZenPing.java:406) > > > > > at java.lang.Thread.run(Thread.java:662) > > > > > [2012-06-04 11:16:38,777][WARN][discovery.zen.ping.multicast] > > > > > [Wilson, Sam] failed to read requesting data from /some ip > > > > > address > > > > > here:54328 > > > > > org.elasticsearch.ElasticSearchIllegalStateException: failed > > > > > multicast message, probably message from previous version > > > > > at > > > > > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > > > $Receiver.run(MulticastZenPing.java:406) > > > > > at java.lang.Thread.run(Thread.java:662) > > > > > > > On Jun 4, 8:19 am, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > I am running Scientific Linux release 6.2 (Carbon). And it's a > > > > > > Openstack virtual instance. > > > > > > > > > Do you use OpenJDK ? > > > > > > > > Yes - it is OpenJDK. > > > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > > > No - didn't change any configuration parameters. I am running > > > > > > the > > > > > > defaults. > > > > > > > > Thanks so much for your help! > > > > > > Karine > > > > > > > > On Jun 3, 9:28 am, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > Lol Ivan ! > > > > > > > Not old, but updates exists 😉 > > > > > > > > > BTW, Karine, are you running on Linux, windows, Mac ? > > > > > > > Do you use OpenJDK ? > > > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > > > > David > > > > > > > > > Le 3 juin 2012 à 17:33, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) a écrit : > > > > > > > > > > A two-month old release is already old? 🙂 > > > > > > > > > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) > > > > > > > > wrote: > > > > > > > > > > > > > > > > > What is your jvm ? > > > > > > > > > ES 0.19.2 is old. Did you try with a more recent version > > > > > > > > > (0.19.4) ? > > > > > > > > > > > David > > > > > > > > > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a > > > > > > > > > écrit : > > > > > > > > > > > > Nope. > > > > > > > > > > > > Also, this is elasticsearch-0.19.2 with mongodb river > > > > > > > > > > plugin. > > > > > > > > > > There was "Segmentation Fault" on the terminal where ES was > > > > > > > > > > running. > > > > > > > > > > > > Thanks, > > > > > > > > > > Kara > > > > > > > > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > Does anyone know why ES terminates itself after indexing x > > > > > > > > > > > number of documents? I restarted it 3 times today. > > > > > > > > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > > > > > > > > ./elasticsearch > > > > > > > > > > > > > Thanks, > > > > > > > > > > > Kara ---
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 4, 2012, 9:49pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/16 "2012-06-04T21:49:18Z")
Just increased the memory. Trying again. I am inserting 100 records then it is inactive and the ES terminates after a while. On Jun 4, 1:42 pm, "David Pilato" [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > Have you tried to give more memory to your instance ? > > How many docs are you sending to your ES instance ? > > David > > > -----Message d'origine----- > > De : [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) > > [[mailto:elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)] De la part de Kara > > Envoyé : lundi 4 juin 2012 22:07 > > À : elasticsearch > > Objet : Re: elasticsearch server terminates itself > > > No - I didn't find any hprof file in the ES directory. > > > Thanks, > > Karine > > > On Jun 4, 12:39 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > Hum... Sounds bad. > > > > You can set logs to trace. See config/logging.yml file. > > > I think that a new Line like following will work: > > > river.mongodb: TRACE > > > > BTW do you see a hprof file or something like that in your es dir ? > > > > Le 4 juin 2012 à 21:26, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > I just do the following: > > > > > > > > > ps -ef | grep elast > > > > > $ ps -ef | grep elas > > > > dib 29863 1 0 11:21 pts/4 00:00:11 > > > > /opt/dsw/java/bin/java -Xms256m -Xmx1g -Xss256k -XX:+UseParNewGC > > > > -XX:+UseConcMarkSweepGC - > > > > XX:CMSInitiatingOccupancyFraction=75 -XX: > > > > +UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError - > > > > Delasticsearch -Des.path.home=/home/dib/elasticsearch-0.19.4 -cp 😕 > > > > home/dib/elasticsearch-0.19.4/lib/_:/home/dib/elasticsearch- > > > > 0.19.4/l > > > > ib/ > > > > sigar/_ org.elasticsearch.bootstrap.Elasticsearch > > > > > I get no results from the "ps -ef | grep elas" when failed and the > > > > curl client doesn't work either. So, no elastic process running at > > > > that time. > > > > > I thought the ES and river are one process. Mongodb servers are > > > > fine > > > > > > > > - just the ES terminates in 1 hour and about 15 minutes. > > > > > How can I check if it's the mongodb river memory usage? > > > > > > Is someone else on the list is using this river in production ? > > > > > I don't know. > > > > > Also, how can I collect more logs? I am hoping to see more in the > > > > log file when it terminates. > > > > > Thanks David! > > > > Karine > > > > On Jun 4, 12:09 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > Fine. Do you mean that the Elasticsearch process stop after 1 hour > > > > > ? > > > > > Or, is it the river that hang after a while ? And you still able > > > > > to gethttp://localhost:9200/? > > > > > > I'm asking that because I got about the same issue with the > > > > > couchDb river some weeks ago. > > > > > > If ES is killed, I think that there's perhaps something wrong in > > > > > the mongodb river (memory usage ?). I did not look at the source code. > > > > > > Is someone else on the list is using this river in production ? > > > > > > David > > > > > > Le 4 juin 2012 à 20:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > > > Hi David, > > > > > > > I installed the ES on the physical box that runs centos and also > > > > > > oracle jdk 1.6. It terminated in 1 hour and 15 minutes again. > > > > > > That's about how much time it takes to terminate itself for all > > > > > > my > > > > > > tries. I got this error this time: Sorry I had to block the ip > > > > > > addresses in the logs. > > > > > > > [2012-06-04 10:04:10,633][INFO][river.mongodb] > > > > > > [Wilson, Sam] [mongodb][mongodb] No known previous slurping time > > > > > > for this collection > > > > > > [2012-06-04 10:04:11,016][INFO][cluster.metadata] > > > > > > [Wilson, Sam] [\_river] update\_mapping [mongodb] (dynamic) > > > > > > [2012-06-04 11:16:37,278][WARN][discovery.zen.ping.multicast] > > > > > > [Wilson, Sam] failed to read requesting data from /some ip > > > > > > address > > > > > > here:54328 > > > > > > org.elasticsearch.ElasticSearchIllegalStateException: failed > > > > > > multicast message, probably message from previous version > > > > > > at > > > > > > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > > > > $Receiver.run(MulticastZenPing.java:406) > > > > > > at java.lang.Thread.run(Thread.java:662) > > > > > > [2012-06-04 11:16:38,777][WARN][discovery.zen.ping.multicast] > > > > > > [Wilson, Sam] failed to read requesting data from /some ip > > > > > > address > > > > > > here:54328 > > > > > > org.elasticsearch.ElasticSearchIllegalStateException: failed > > > > > > multicast message, probably message from previous version > > > > > > at > > > > > > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > > > > $Receiver.run(MulticastZenPing.java:406) > > > > > > at java.lang.Thread.run(Thread.java:662) > > > > > > > On Jun 4, 8:19 am, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > I am running Scientific Linux release 6.2 (Carbon). And it's a > > > > > > > Openstack virtual instance. > > > > > > > > > Do you use OpenJDK ? > > > > > > > > Yes - it is OpenJDK. > > > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > > > No - didn't change any configuration parameters. I am running > > > > > > > the > > > > > > > defaults. > > > > > > > > Thanks so much for your help! > > > > > > > Karine > > > > > > > > On Jun 3, 9:28 am, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > Lol Ivan ! > > > > > > > > Not old, but updates exists 😉 > > > > > > > > > BTW, Karine, are you running on Linux, windows, Mac ? > > > > > > > > Do you use OpenJDK ? > > > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > > > > David > > > > > > > > > Le 3 juin 2012 à 17:33, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) a écrit : > > > > > > > > > > A two-month old release is already old? 🙂 > > > > > > > > > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > What is your jvm ? > > > > > > > > > > ES 0.19.2 is old. Did you try with a more recent version > > > > > > > > > > (0.19.4) ? > > > > > > > > > > > David > > > > > > > > > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a > > > > > > > > > > écrit : > > > > > > > > > > > > Nope. > > > > > > > > > > > > Also, this is elasticsearch-0.19.2 with mongodb river > > > > > > > > > > > plugin. > > > > > > > > > > > There was "Segmentation Fault" on the terminal where ES was > > > > > > > > > > > running. > > > > > > > > > > > > Thanks, > > > > > > > > > > > Kara > > > > > > > > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > Does anyone know why ES terminates itself after indexing x > > > > > > > > > > > > number of documents? I restarted it 3 times today. > > > > > > > > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > > > > > > > > ./elasticsearch > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Kara ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [June 4, 2012, 10:30pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/17 "2012-06-04T22:30:07Z")
Hi Kara, Messages like "org.elasticsearch.ElasticSearchIllegalStateException: failed multicast message, probably message from previous version" are mostly unusual. They are harmless but could indicate setup problems. Do you use several Elasticsearch versions, on different nodes? Did you upgrade before? Cheers, Jörg On Monday, June 4, 2012 11:49:18 PM UTC+2, Kara wrote: > Just increased the memory. Trying again. > > I am inserting 100 records then it is inactive and the ES terminates > after a while. > > On Jun 4, 1:42 pm, "David Pilato" [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > Have you tried to give more memory to your instance ? > > > > How many docs are you sending to your ES instance ? > > > > David > > > > > -----Message d'origine----- > > > De : [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) > > > [[mailto:elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)] De la part de Kara > > > Envoyé : lundi 4 juin 2012 22:07 > > > À : elasticsearch > > > Objet : Re: elasticsearch server terminates itself > > > > > No - I didn't find any hprof file in the ES directory. > > > > > Thanks, > > > Karine > > > > > On Jun 4, 12:39 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > Hum... Sounds bad. > > > > > > You can set logs to trace. See config/logging.yml file. > > > > I think that a new Line like following will work: > > > > river.mongodb: TRACE > > > > > > BTW do you see a hprof file or something like that in your es dir ? > > > > > > Le 4 juin 2012 à 21:26, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > > > I just do the following: > > > > > > > > > > > ps -ef | grep elast > > > > > > > $ ps -ef | grep elas > > > > > dib 29863 1 0 11:21 pts/4 00:00:11 > > > > > /opt/dsw/java/bin/java -Xms256m -Xmx1g -Xss256k -XX:+UseParNewGC > > > > > -XX:+UseConcMarkSweepGC - > > > > > XX:CMSInitiatingOccupancyFraction=75 -XX: > > > > > +UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError - > > > > > Delasticsearch -Des.path.home=/home/dib/elasticsearch-0.19.4 -cp > > > > > 😕 > > > > > home/dib/elasticsearch-0.19.4/lib/_:/home/dib/elasticsearch- > > > > > 0.19.4/l > > > > > ib/ > > > > > sigar/_ org.elasticsearch.bootstrap.Elasticsearch > > > > > > > I get no results from the "ps -ef | grep elas" when failed and the > > > > > curl client doesn't work either. So, no elastic process running at > > > > > that time. > > > > > > > I thought the ES and river are one process. Mongodb servers are > > > > > fine > > > > > > > > > > - just the ES terminates in 1 hour and about 15 minutes. > > > > > > > How can I check if it's the mongodb river memory usage? > > > > > > > > Is someone else on the list is using this river in production ? > > > > > > I don't know. > > > > > > > Also, how can I collect more logs? I am hoping to see more in the > > > > > log file when it terminates. > > > > > > > Thanks David! > > > > > Karine > > > > > On Jun 4, 12:09 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > > > Fine. Do you mean that the Elasticsearch process stop after 1 > > > > > > hour > > > > > > ? > > > > > > Or, is it the river that hang after a while ? And you still able > > > > > > to gethttp://localhost:9200/? > > > > > > > > I'm asking that because I got about the same issue with the > > > > > > couchDb river some weeks ago. > > > > > > > > If ES is killed, I think that there's perhaps something wrong in > > > > > > the mongodb river (memory usage ?). I did not look at the source code. > > > > > > > > Is someone else on the list is using this river in production ? > > > > > > > > David > > > > > > > > Le 4 juin 2012 à 20:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit > > > > > > : > > > > > > > > > Hi David, > > > > > > > > > I installed the ES on the physical box that runs centos and also > > > > > > > oracle jdk 1.6. It terminated in 1 hour and 15 minutes again. > > > > > > > That's about how much time it takes to terminate itself for all > > > > > > > my > > > > > > > tries. I got this error this time: Sorry I had to block the ip > > > > > > > addresses in the logs. > > > > > > > > > [2012-06-04 10:04:10,633][INFO][river.mongodb] > > > > > > > [Wilson, Sam] [mongodb][mongodb] No known previous slurping time > > > > > > > for this collection > > > > > > > [2012-06-04 10:04:11,016][INFO][cluster.metadata] > > > > > > > [Wilson, Sam] [\_river] update\_mapping [mongodb] (dynamic) > > > > > > > [2012-06-04 11:16:37,278][WARN][discovery.zen.ping.multicast] > > > > > > > [Wilson, Sam] failed to read requesting data from /some ip > > > > > > > address > > > > > > > here:54328 > > > > > > > org.elasticsearch.ElasticSearchIllegalStateException: failed > > > > > > > multicast message, probably message from previous version > > > > > > > at > > > > > > > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > > > > > $Receiver.run(MulticastZenPing.java:406) > > > > > > > at java.lang.Thread.run(Thread.java:662) > > > > > > > [2012-06-04 11:16:38,777][WARN][discovery.zen.ping.multicast] > > > > > > > [Wilson, Sam] failed to read requesting data from /some ip > > > > > > > address > > > > > > > here:54328 > > > > > > > org.elasticsearch.ElasticSearchIllegalStateException: failed > > > > > > > multicast message, probably message from previous version > > > > > > > at > > > > > > > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > > > > > $Receiver.run(MulticastZenPing.java:406) > > > > > > > at java.lang.Thread.run(Thread.java:662) > > > > > > > > > On Jun 4, 8:19 am, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > > > I am running Scientific Linux release 6.2 (Carbon). And it's a > > > > > > > > Openstack virtual instance. > > > > > > > > > > > Do you use OpenJDK ? > > > > > > > > > > Yes - it is OpenJDK. > > > > > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > > > > > No - didn't change any configuration parameters. I am running > > > > > > > > the > > > > > > > > defaults. > > > > > > > > > > Thanks so much for your help! > > > > > > > > Karine > > > > > > > > > > On Jun 3, 9:28 am, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > > > Lol Ivan ! > > > > > > > > > Not old, but updates exists 😉 > > > > > > > > > > > BTW, Karine, are you running on Linux, windows, Mac ? > > > > > > > > > Do you use OpenJDK ? > > > > > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > > > > > > David > > > > > > > > > > > Le 3 juin 2012 à 17:33, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) a écrit > > > > > > > > > : > > > > > > > > > > > > A two-month old release is already old? 🙂 > > > > > > > > > > > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) > > > > wrote: > > > > > > > > > > > > > > What is your jvm ? > > > > > > > > > > > ES 0.19.2 is old. Did you try with a more recent version > > > > > > > > > > > (0.19.4) ? > > > > > > > > > > > > > David > > > > > > > > > > > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a > > > > > > > > > > > écrit : > > > > > > > > > > > > > > Nope. > > > > > > > > > > > > > > Also, this is elasticsearch-0.19.2 with mongodb river > > > > > > > > > > > > plugin. > > > > > > > > > > > > There was "Segmentation Fault" on the terminal where ES was > > > > > > > > > > > > running. > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Kara > > > > > > > > > > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > Does anyone know why ES terminates itself after indexing x > > > > > > > > > > > > > number of documents? I restarted it 3 times today. > > > > > > > > > > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > > > > > > > > > > ./elasticsearch > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > Kara ---
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 4, 2012, 10:40pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/18 "2012-06-04T22:40:51Z")
Somebody else started a elasticsearch server on his machine without the mongodb river. He terminated it to troubleshoot this problem first. I don't see anything in the log file now but it still terminates itself after awhile. I have to say that I am leaving the ES server inactive for 1 hour and 15 minutes then it terminates. Next I will try to keep the ES server busy to see if it terminates itself even when it's busy. Thanks! Kara On Jun 4, 3:30 pm, Jörg Prante [joergpra...@gmail.com](mailto:joergpra...@gmail.com) wrote: > Hi Kara, > > Messages like "org.elasticsearch.ElasticSearchIllegalStateException: failed > multicast message, probably message from previous version" are mostly > unusual. They are harmless but could indicate setup problems. Do you use > several Elasticsearch versions, on different nodes? Did you upgrade before? > > Cheers, > > Jörg > > On Monday, June 4, 2012 11:49:18 PM UTC+2, Kara wrote: > > > Just increased the memory. Trying again. > > > I am inserting 100 records then it is inactive and the ES terminates > > after a while. > > > On Jun 4, 1:42 pm, "David Pilato" [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > Have you tried to give more memory to your instance ? > > > > How many docs are you sending to your ES instance ? > > > > David > > > > > -----Message d'origine----- > > > > De : [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) > > > > [[mailto:elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)] De la part de Kara > > > > Envoyé : lundi 4 juin 2012 22:07 > > > > À : elasticsearch > > > > Objet : Re: elasticsearch server terminates itself > > > > > No - I didn't find any hprof file in the ES directory. > > > > > Thanks, > > > > Karine > > > > > On Jun 4, 12:39 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > Hum... Sounds bad. > > > > > > You can set logs to trace. See config/logging.yml file. > > > > > I think that a new Line like following will work: > > > > > river.mongodb: TRACE > > > > > > BTW do you see a hprof file or something like that in your es dir ? > > > > > > Le 4 juin 2012 à 21:26, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit : > > > > > > > I just do the following: > > > > > > > > > > > > > ps -ef | grep elast > > > > > > > $ ps -ef | grep elas > > > > > > dib 29863 1 0 11:21 pts/4 00:00:11 > > > > > > /opt/dsw/java/bin/java -Xms256m -Xmx1g -Xss256k -XX:+UseParNewGC > > > > > > -XX:+UseConcMarkSweepGC - > > > > > > XX:CMSInitiatingOccupancyFraction=75 -XX: > > > > > > +UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError - > > > > > > Delasticsearch -Des.path.home=/home/dib/elasticsearch-0.19.4 -cp > > > > > > 😕 > > > > > > home/dib/elasticsearch-0.19.4/lib/_:/home/dib/elasticsearch- > > > > > > 0.19.4/l > > > > > > ib/ > > > > > > sigar/_ org.elasticsearch.bootstrap.Elasticsearch > > > > > > > I get no results from the "ps -ef | grep elas" when failed and the > > > > > > curl client doesn't work either. So, no elastic process running at > > > > > > that time. > > > > > > > I thought the ES and river are one process. Mongodb servers are > > > > > > fine > > > > > > > > > > > > - just the ES terminates in 1 hour and about 15 minutes. > > > > > > > How can I check if it's the mongodb river memory usage? > > > > > > > > Is someone else on the list is using this river in production ? > > > > > > > I don't know. > > > > > > > Also, how can I collect more logs? I am hoping to see more in the > > > > > > log file when it terminates. > > > > > > > Thanks David! > > > > > > Karine > > > > > > On Jun 4, 12:09 pm, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > > > > > Fine. Do you mean that the Elasticsearch process stop after 1 > > > > > > > hour > > > > > > > ? > > > > > > > Or, is it the river that hang after a while ? And you still able > > > > > > > to gethttp://localhost:9200/? > > > > > > > > I'm asking that because I got about the same issue with the > > > > > > > couchDb river some weeks ago. > > > > > > > > If ES is killed, I think that there's perhaps something wrong in > > > > > > > the mongodb river (memory usage ?). I did not look at the source code. > > > > > > > > Is someone else on the list is using this river in production ? > > > > > > > > David > > > > > > > > Le 4 juin 2012 à 20:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a écrit > > > > > > > : > > > > > > > > > Hi David, > > > > > > > > > I installed the ES on the physical box that runs centos and also > > > > > > > > oracle jdk 1.6. It terminated in 1 hour and 15 minutes again. > > > > > > > > That's about how much time it takes to terminate itself for all > > > > > > > > my > > > > > > > > tries. I got this error this time: Sorry I had to block the ip > > > > > > > > addresses in the logs. > > > > > > > > > [2012-06-04 10:04:10,633][INFO][river.mongodb] > > > > > > > > [Wilson, Sam] [mongodb][mongodb] No known previous slurping time > > > > > > > > for this collection > > > > > > > > [2012-06-04 10:04:11,016][INFO][cluster.metadata] > > > > > > > > [Wilson, Sam] [\_river] update\_mapping [mongodb] (dynamic) > > > > > > > > [2012-06-04 11:16:37,278][WARN][discovery.zen.ping.multicast] > > > > > > > > [Wilson, Sam] failed to read requesting data from /some ip > > > > > > > > address > > > > > > > > here:54328 > > > > > > > > org.elasticsearch.ElasticSearchIllegalStateException: failed > > > > > > > > multicast message, probably message from previous version > > > > > > > > at > > > > > > > > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > > > > > > $Receiver.run(MulticastZenPing.java:406) > > > > > > > > at java.lang.Thread.run(Thread.java:662) > > > > > > > > [2012-06-04 11:16:38,777][WARN][discovery.zen.ping.multicast] > > > > > > > > [Wilson, Sam] failed to read requesting data from /some ip > > > > > > > > address > > > > > > > > here:54328 > > > > > > > > org.elasticsearch.ElasticSearchIllegalStateException: failed > > > > > > > > multicast message, probably message from previous version > > > > > > > > at > > > > > > > > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing > > > > > > > > $Receiver.run(MulticastZenPing.java:406) > > > > > > > > at java.lang.Thread.run(Thread.java:662) > > > > > > > > > On Jun 4, 8:19 am, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > > > > > I am running Scientific Linux release 6.2 (Carbon). And it's a > > > > > > > > > Openstack virtual instance. > > > > > > > > > > > Do you use OpenJDK ? > > > > > > > > > > Yes - it is OpenJDK. > > > > > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > > > > > No - didn't change any configuration parameters. I am running > > > > > > > > > the > > > > > > > > > defaults. > > > > > > > > > > Thanks so much for your help! > > > > > > > > > Karine > > > > > > > > > > On Jun 3, 9:28 am, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote: > > > > > > > > > > > Lol Ivan ! > > > > > > > > > > Not old, but updates exists 😉 > > > > > > > > > > > BTW, Karine, are you running on Linux, windows, Mac ? > > > > > > > > > > Do you use OpenJDK ? > > > > > > > > > > > Did you modify something in config files (memory settings ?) > > > > > > > > > > > David > > > > > > > > > > > Le 3 juin 2012 à 17:33, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) a écrit > > > > > > > > > > : > > > > > > > > > > > > A two-month old release is already old? 🙂 > > > > > > > > > > > > On Fri, Jun 1, 2012 at 3:50 PM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) > > > > > wrote: > > > > > > > > > > > > > > > > What is your jvm ? > > > > > > > > > > > > ES 0.19.2 is old. Did you try with a more recent version > > > > > > > > > > > > (0.19.4) ? > > > > > > > > > > > > > David > > > > > > > > > > > > > Le 1 juin 2012 à 23:32, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) a > > > > > > > > > > > > écrit : > > > > > > > > > > > > > > Nope. > > > > > > > > > > > > > > Also, this is elasticsearch-0.19.2 with mongodb river > > > > > > > > > > > > > plugin. > > > > > > > > > > > > > There was "Segmentation Fault" on the terminal where ES was > > > > > > > > > > > > > running. > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > Kara > > > > > > > > > > > > > > On Jun 1, 1:21 pm, Kara [karine.marab...@aero.org](mailto:karine.marab...@aero.org) wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > Does anyone know why ES terminates itself after indexing x > > > > > > > > > > > > > > number of documents? I restarted it 3 times today. > > > > > > > > > > > > > > > This is how I start the server. Not passing any arguments. > > > > > > > > > > > > > > > > ./elasticsearch > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > Kara ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [June 4, 2012, 10:58pm UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/19 "2012-06-04T22:58:15Z")
OK, so I think it is the segmentation fault of the JVM that is causing the trouble. Maybe running ES under the service wrapper helps, chances are it will write some messages in the wrapper.log. There should be crash files (hs\_err\_pid...log). If there are no JVM crash files, a good idea is to enable core dumps (ulimit -c) and examine those dumps by gdb if a segfault happens again. Another hint is to disable the sigar libs, but I really don't know if sigar works reliably on OpenStack virtual instances. Jörg On Tuesday, June 5, 2012 12:40:51 AM UTC+2, Kara wrote: > Somebody else started a elasticsearch server on his machine without > the mongodb river. He terminated it to troubleshoot this problem > first. I don't see anything in the log file now but it still > terminates itself after awhile. I have to say that I am leaving the ES > server inactive for 1 hour and 15 minutes then it terminates. Next I > will try to keep the ES server busy to see if it terminates itself > even when it's busy. ---
**Author:** ![Kara](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@Kara](https://discuss.elastic.co/u/Kara)\ **Post date:** [June 5, 2012, 4:10am UTC](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945/20 "2012-06-05T04:10:39Z")
The service wrapper is going to restart the jvm correct? But at that time I'll be dropping data that mongodb streams to ES. On Jun 4, 3:58 pm, Jörg Prante [joergpra...@gmail.com](mailto:joergpra...@gmail.com) wrote: > OK, so I think it is the segmentation fault of the JVM that is causing the > trouble. Maybe running ES under the service wrapper helps, chances are it > will write some messages in the wrapper.log. There should be crash files > (hs\_err\_pid...log). If there are no JVM crash files, a good idea is to > enable core dumps (ulimit -c) and examine those dumps by gdb if a segfault > happens again. > Another hint is to disable the sigar libs, but I really don't know if sigar > works reliably on OpenStack virtual instances. > > Jörg > > On Tuesday, June 5, 2012 12:40:51 AM UTC+2, Kara wrote: > > > Somebody else started a elasticsearch server on his machine without > > the mongodb river. He terminated it to troubleshoot this problem > > first. I don't see anything in the log file now but it still > > terminates itself after awhile. I have to say that I am leaving the ES > > server inactive for 1 hour and 15 minutes then it terminates. Next I > > will try to keep the ES server busy to see if it terminates itself > > even when it's busy.- Hide quoted text - > > - Show quoted text - [Next page](https://discuss.elastic.co/t/elasticsearch-server-terminates-itself/7945.md?page=2)