# Elasticsearch seems to appear unreachble or down **URL:** \ **Category:** Elasticsearch\ **Created:** [November 17, 2015, 10:00pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857 "2015-11-17T22:00:10Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\ **Post date:** [November 17, 2015, 10:00pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/1 "2015-11-17T22:00:10Z")
Im getting this error in my logstash logfile. :message=\>"Attempted to send a bulk request to Elasticsearch configured at '["[http://localhost:9200/](http://localhost:9200/)"]', but Elasticsearch appears to be unreachable or down!", Data is still flowing through kibana though. I check service elasticsearch status and its running. Logstash config: output { elasticsearch { hosts =\> ["127.0.0.1(I've tried this and localhost):9200"] } stdout { codec =\> rubydebug } } ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 17, 2015, 10:00pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/2 "2015-11-17T22:00:34Z")
And have you checked ES as well? ---
**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\ **Post date:** [November 17, 2015, 10:02pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/3 "2015-11-17T22:02:03Z")
Yes, no error in the log. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 17, 2015, 10:52pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/4 "2015-11-17T22:52:19Z")
Right, but what state is it in? ---
**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\ **Post date:** [November 18, 2015, 3:03pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/5 "2015-11-18T15:03:46Z")
[2015-11-18 15:01:50,091][INFO][discovery] [William Stryker] elasticsearch/R3Ar2QRSR2io1HL9AwvuQw [2015-11-18 15:01:53,116][INFO][cluster.service] [William Stryker] new\_master {William Stryker}{R3Ar2QRSR2io1HL9AwvuQw}{127.0.0.1}{localhost/127.0.0.1:9300}, reason: zen-disco-join(elected\_as\_master, [0] joins received) [2015-11-18 15:01:53,150][INFO][http] [William Stryker] publish\_address {localhost/127.0.0.1:9200}, bound\_addresses {127.0.0.1:9200}, {[::1]:9200} [2015-11-18 15:01:53,151][INFO][node] [William Stryker] started [2015-11-18 15:01:53,185][INFO][gateway] [William Stryker] recovered [4] indices into cluster\_state ---
**Author:** ![lwintergerst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lwintergerst/32/18164_2.png) [@lwintergerst](https://discuss.elastic.co/u/lwintergerst)\ **Post date:** [November 18, 2015, 3:08pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/6 "2015-11-18T15:08:31Z")
can you post the output of a curl on "[http://localhost:9200](http://localhost:9200)"? ---
**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\ **Post date:** [November 18, 2015, 3:12pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/7 "2015-11-18T15:12:45Z")
{ "name" : "William Stryker", "cluster\_name" : "elasticsearch", "version" : { "number" : "2.0.0", "build\_hash" : "de54438d6af8f9340d50c5c786151783ce7d6be5", "build\_timestamp" : "2015-10-22T08:09:48Z", "build\_snapshot" : false, "lucene\_version" : "5.2.1" }, "tagline" : "You Know, for Search" } ---
**Author:** ![lwintergerst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lwintergerst/32/18164_2.png) [@lwintergerst](https://discuss.elastic.co/u/lwintergerst)\ **Post date:** [November 18, 2015, 3:15pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/8 "2015-11-18T15:15:30Z")
Are there many tasks pending? 9200/\_cluster/pending\_tasks?pretty Did you try to restart your cluster already? If so, did the same problem occur again? Did you try to restart your logstash? ---
**Author:** ![lwintergerst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lwintergerst/32/18164_2.png) [@lwintergerst](https://discuss.elastic.co/u/lwintergerst)\ **Post date:** [November 18, 2015, 3:16pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/9 "2015-11-18T15:16:10Z")
and also, please post the output of the following: ...9200/\_cluster/health?pretty=true ---
**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\ **Post date:** [November 18, 2015, 5:18pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/10 "2015-11-18T17:18:38Z")
yes i restarted all services and no changes. Output: { "cluster\_name" : "elasticsearch", "status" : "yellow", "timed\_out" : false, "number\_of\_nodes" : 1, "number\_of\_data\_nodes" : 1, "active\_primary\_shards" : 16, "active\_shards" : 16, "relocating\_shards" : 0, "initializing\_shards" : 0, "unassigned\_shards" : 16, "delayed\_unassigned\_shards" : 0, "number\_of\_pending\_tasks" : 0, "number\_of\_in\_flight\_fetch" : 0, "task\_max\_waiting\_in\_queue\_millis" : 0, "active\_shards\_percent\_as\_number" : 50.0 } ---
**Author:** ![msimos](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@msimos](https://discuss.elastic.co/u/msimos)\ **Post date:** [November 18, 2015, 7:33pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/11 "2015-11-18T19:33:24Z")
Try running logstash with --debug and see if you get any other error messages. Also since you're using Elasticsearch 2.0, make sure you're using Logstash 2.0. Only Logstash 2.0 is compatible with Elasticsearch 2.0. ---
**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\ **Post date:** [November 19, 2015, 12:52am UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/12 "2015-11-19T00:52:50Z")
Default settings used: Filter workers: 4 Starting courier input listener {:address=\>"0.0.0.0:9006", :level=\>:info, :file=\>"logstash/inputs/courier.rb", :line=\>"102", :method=\>"register"} The error reported is: input/courier: Failed to initialise: Address already in use - bind - Address already in use Im getting this error but the port is linked to that logstash instance. ---
**Author:** ![kmroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kmroz/32/62741_2.png) [@kmroz](https://discuss.elastic.co/u/kmroz)\ **Post date:** [November 20, 2015, 10:12pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/13 "2015-11-20T22:12:56Z")
Any help on this issue? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:36pm UTC](https://discuss.elastic.co/t/elasticsearch-seems-to-appear-unreachble-or-down/34857/14 "2017-07-05T23:36:49Z")