Elasticsearch server terminates itself

Elastic Stack Elasticsearch
1

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

2

Anything in logs ?

David :wink:
Twitter : @dadoonet / @elasticsearchfr

Le 1 juin 2012 à 22:21, Kara 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

3

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 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

4

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 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 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

5

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 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 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 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

6

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 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 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 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 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 -
7

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

8

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit :

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

9

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 wrote:

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit :

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

10

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 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 wrote:

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit :

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

11

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/ ?

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 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 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 wrote:

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit :

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

12

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 :confused:
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 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 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 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 wrote:

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit :

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

13

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 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 :confused:
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 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 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 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 wrote:

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit :

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

14

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 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 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 :confused:
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 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 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 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 wrote:

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit :

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

15

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] 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 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 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 :confused:
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 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 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 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 wrote:

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit :

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

16

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 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] 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 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 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 :confused:
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 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 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 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 wrote:

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit :

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

17

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 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] 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 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 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
:confused:
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 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 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 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 wrote:

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit
:

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

18

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 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 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] 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 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 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
:confused:
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 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 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 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 wrote:

Lol Ivan !
Not old, but updates exists :wink:

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 a écrit
:

A two-month old release is already old? :slight_smile:

On Fri, Jun 1, 2012 at 3:50 PM, David Pilato 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 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 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

19

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.

20

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 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 -