ruby on rails - Why does "rake elasticsearch:start" timeout but still start an elasticsearch node? -

After months of elasticsearch and rspec working together altogether, I have many new and seemingly random Faraday: getting timeout error

Errors when I run rspec , and I'm trying to troubleshoot the problem I have a classic Started with resumption from there I saw what elastic search was doing. First of all, I ran this:

  $ curl localhost: 9200 {"status": 200, "name": "resellion recorder", "cluster_name": "elasticsearch_eliduke", "version": { "number": "1.4.2", "build_hash": "927caff6f05403e936c20bf4529f144f0c89fd8c", "build_timestamp": "2014-12-16T14: 11: 12Z", "build_snapshot": false, "lucene_version": "4.10.2"} "Tagline": "You know, for search"}  

So in any way I have a lively resume immediately after the elasticsearch is running. Is there a reboot in some way? I thought that maybe something in my .bash_profile might be, but nothing.

Then I checked my elastic search test ports:

  $ curl localhost: 9250 curl: (7) failed to connect to localhost port 9250: reject connection Given  

Obviously, the test node is not running, so I tried to use the rake work:

  $ rack elastic search : Start 2 flexible detective nodes start ........... rack canceled! Timeout :: Error: Expiration Expiration / Users / LYDUK / Arvim / games / RB -2 -2klk0 / games / Selastiksserch-extension -1.0.17 / lib / Lolsishachc / extensions / Test / Clstrkarbi `loop in 2002 22:" block (Level 2) __wait_for_status / Users / Eliduke / Krvm / games / Ruby-2.1.0 / games / Elastiksearc-Extensions-0k0kl7 / lib / Elastiksearc / Extensions / Test / Clstrkrb: 220: these /ussers/eliduke/krvm/gems/rubi -2.1.0 / gems / elasticsearch-extensions-0.0.17 / lib / elasticsearch / extensions / test / cluster.rb: 220: in '__wait_for_status block' / users / eliduke / .rvm / gemstone / ruby ​​2.1.0 / Gems / elasticsearch- extension -0k0kl7 / Lib / Elasticsearch / extension / test / cluster.rb: 219: ` '/Users/eliduke/.rvm/gems /ruby-2.1.0/ge in __wait_for_status MS / Elastiksearc-Extensions-0k0kl7 / lib / Elastiksearc / Extensions / Test / Clstrkrb: 201: in `Vet_for_grin '/ussers/eliduke/krvm/gems/rubi-2klk0 / games / Elastiksearc-Akstenshns- 0.0.17 / lib / elasticsearch / extensions / test / cluster.rb: 125: IN 'Start' / Users / LIDEUK / RVM / Games / RB -2.2.0 / Games / Segalasttextures-Extensions -0.0.17 / lib / elasticsearch / exte Nsions / test / cluster / taskss.rb: 6: `in block (2 level) & lt; Top (required) & gt; /ussers/eliduke/krvm/gems/rubi-2klk0/bin/rubi_aksekyutable_huks:l5:in `Avl '/ussers/eliduke/krvm/gems/rubi-2klk0/bin/rubi_aksekyutable_huks: 15: In` & Lt; Main & gt; 'Function: Top = & gt; Elasticsearch: Start (Completing the task running with --trace)  

It seemed as though it was starting correctly because these small dots crawled on the screen But then Bongoos ! Who knows what it is due to the timeout: It was only trying to start for 20 or 30 seconds. But then weird part:

  $ curl localhost: 9250 {"status": 200, "name": "node-1", "cluster_name": "elasticsearch_test", "version": { "Number": "1.4.2", "build_hash": "927caff6f05403e936c20bf4529f144f0c89fd8c", "build_timestamp": "2014-12-16T14: 11: 12Z", "build_snapshot": false, "lucene_version": "4.10.2"} , "Tagline": "you know, to search"}  

did it start anyway?! Very weird Something seems wrong here, so I thought I just want to throw this out there and see if anyone else has had this problem.

1. Do you know why the elasticsearch at Port 9200 has already started after reboot? ?
2. You know why do rake elasticsearch work: TimeoutError error has any connection: start will be timed out
3. My Faraday does this to all?
4. Is there a good next step to troubleshoot this problem?