Elasticsearch not responding


(michaelpeters99) #1

I failed to recover from running out of file descriptors, so eventually re-installed 0.17.6. But after days of trying lots of things, :9200 just does not respond. I am installing on Centos 6 and elasticsearch previously ran fine on this server for over three months.
I am sure I am doing something silly and would really appreciate some help. The log on a clean install is as below:

[2012-02-27 09:18:34,142][INFO ][node ] [Living Mummy] {elasticsearch/0.17.6}[13076]: initializing ...
[2012-02-27 09:18:34,149][INFO ][plugins ] [Living Mummy] loaded [], sites []
[2012-02-27 09:18:36,401][INFO ][node ] [Living Mummy] {elasticsearch/0.17.6}[13076]: initialized
[2012-02-27 09:18:36,401][INFO ][node ] [Living Mummy] {elasticsearch/0.17.6}[13076]: starting ...
[2012-02-27 09:18:36,544][INFO ][transport ] [Living Mummy] bound_address {inet[/0:0:0:0:0:0:0:0:9318]}, publish_address {inet[/78.31.111.84:9318]}
[2012-02-27 09:18:39,569][INFO ][cluster.service ] [Living Mummy] new_master [Living Mummy][9sENJgbwQma4LnI-7nwJIQ][inet[/78.31.111.84:9318]], reason: zen-disco-join (elected_as_master)
[2012-02-27 09:18:39,621][INFO ][discovery ] [Living Mummy] elastictwin/9sENJgbwQma4LnI-7nwJIQ
[2012-02-27 09:18:39,675][INFO ][http ] [Living Mummy] bound_address {inet[/0:0:0:0:0:0:0:0:9218]}, publish_address {inet[/78.31.111.84:9218]}
[2012-02-27 09:18:39,677][INFO ][node ] [Living Mummy] {elasticsearch/0.17.6}[13076]: started
[2012-02-27 09:18:39,695][INFO ][gateway ] [Living Mummy] recovered [0] indices into cluster_state

Thanks, Mike


(Rafał Kuć) #2

Hello,

It seems, that Your instance was not bound to 9200 and 9300. From the
logs it seems that Elasticsearch was bound to 78.31.111.84:9318 and
78.31.111.84:9218. Please try those IP addresses and port 9218 instead
of 9200. Could it be, that something else is bound to 9200 and 9300
ports ?

Regards,
Rafał Kuć
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch

On 27 Lut, 11:09, michaelpeters99 michael.pet...@pobox.com wrote:

I failed to recover from running out of file descriptors, so eventually
re-installed 0.17.6. But after days of trying lots of things, :9200 just
does not respond. I am installing on Centos 6 and elasticsearch previously
ran fine on this server for over three months.
I am sure I am doing something silly and would really appreciate some help.
The log on a clean install is as below:

[2012-02-27 09:18:34,142][INFO ][node ] [Living Mummy]
{elasticsearch/0.17.6}[13076]: initializing ...
[2012-02-27 09:18:34,149][INFO ][plugins ] [Living Mummy]
loaded [], sites []
[2012-02-27 09:18:36,401][INFO ][node ] [Living Mummy]
{elasticsearch/0.17.6}[13076]: initialized
[2012-02-27 09:18:36,401][INFO ][node ] [Living Mummy]
{elasticsearch/0.17.6}[13076]: starting ...
[2012-02-27 09:18:36,544][INFO ][transport ] [Living Mummy]
bound_address {inet[/0:0:0:0:0:0:0:0:9318]}, publish_address
{inet[/78.31.111.84:9318]}
[2012-02-27 09:18:39,569][INFO ][cluster.service ] [Living Mummy]
new_master [Living Mummy][9sENJgbwQma4LnI-7nwJIQ][inet[/78.31.111.84:9318]],
reason: zen-disco-join (elected_as_master)
[2012-02-27 09:18:39,621][INFO ][discovery ] [Living Mummy]
elastictwin/9sENJgbwQma4LnI-7nwJIQ
[2012-02-27 09:18:39,675][INFO ][http ] [Living Mummy]
bound_address {inet[/0:0:0:0:0:0:0:0:9218]}, publish_address
{inet[/78.31.111.84:9218]}
[2012-02-27 09:18:39,677][INFO ][node ] [Living Mummy]
{elasticsearch/0.17.6}[13076]: started
[2012-02-27 09:18:39,695][INFO ][gateway ] [Living Mummy]
recovered [0] indices into cluster_state

Thanks, Mike

--
View this message in context:http://elasticsearch-users.115913.n3.nabble.com/elasticsearch-not-res...
Sent from the ElasticSearch Users mailing list archive at Nabble.com.


(Shay Banon) #3

Note, elasticsearch will try and work with multiple instances on the same data location. Check the data directory and see if multiple nodes were started by mistake.

Regarding ports, it will try and bind to 9200 (HTTP) and 9300 (transport), and if it can't, it will try the next port free.

On Monday, February 27, 2012 at 12:16 PM, Rafał Kuć wrote:

Hello,

It seems, that Your instance was not bound to 9200 and 9300. From the
logs it seems that Elasticsearch was bound to 78.31.111.84:9318 and
78.31.111.84:9218. Please try those IP addresses and port 9218 instead
of 9200. Could it be, that something else is bound to 9200 and 9300
ports ?

Regards,
Rafał Kuć
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch

On 27 Lut, 11:09, michaelpeters99 <michael.pet...@pobox.com (http://pobox.com)> wrote:

I failed to recover from running out of file descriptors, so eventually
re-installed 0.17.6. But after days of trying lots of things, :9200 just
does not respond. I am installing on Centos 6 and elasticsearch previously
ran fine on this server for over three months.
I am sure I am doing something silly and would really appreciate some help.
The log on a clean install is as below:

[2012-02-27 09:18:34,142][INFO ][node ] [Living Mummy]
{elasticsearch/0.17.6}[13076]: initializing ...
[2012-02-27 09:18:34,149][INFO ][plugins ] [Living Mummy]
loaded [], sites []
[2012-02-27 09:18:36,401][INFO ][node ] [Living Mummy]
{elasticsearch/0.17.6}[13076]: initialized
[2012-02-27 09:18:36,401][INFO ][node ] [Living Mummy]
{elasticsearch/0.17.6}[13076]: starting ...
[2012-02-27 09:18:36,544][INFO ][transport ] [Living Mummy]
bound_address {inet[/0:0:0:0:0:0:0:0:9318]}, publish_address
{inet[/78.31.111.84:9318]}
[2012-02-27 09:18:39,569][INFO ][cluster.service ] [Living Mummy]
new_master [Living Mummy][9sENJgbwQma4LnI-7nwJIQ][inet[/78.31.111.84:9318]],
reason: zen-disco-join (elected_as_master)
[2012-02-27 09:18:39,621][INFO ][discovery ] [Living Mummy]
elastictwin/9sENJgbwQma4LnI-7nwJIQ
[2012-02-27 09:18:39,675][INFO ][http ] [Living Mummy]
bound_address {inet[/0:0:0:0:0:0:0:0:9218]}, publish_address
{inet[/78.31.111.84:9218]}
[2012-02-27 09:18:39,677][INFO ][node ] [Living Mummy]
{elasticsearch/0.17.6}[13076]: started
[2012-02-27 09:18:39,695][INFO ][gateway ] [Living Mummy]
recovered [0] indices into cluster_state

Thanks, Mike

--
View this message in context:http://elasticsearch-users.115913.n3.nabble.com/elasticsearch-not-res...
Sent from the ElasticSearch Users mailing list archive at Nabble.com (http://Nabble.com).


(system) #4