# Openshift problem with logstash in other server

**URL:** <https://discuss.elastic.co/t/openshift-problem-with-logstash-in-other-server/316157>\
**Category:** Elasticsearch\
**Created:** [October 9, 2022, 7:06pm UTC](https://discuss.elastic.co/t/openshift-problem-with-logstash-in-other-server/316157 "2022-10-09T19:06:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nikolas1306](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikolas1306/32/111507_2.png) [@Nikolas1306](https://discuss.elastic.co/u/Nikolas1306)\
**Post date:** [October 9, 2022, 7:06pm UTC](https://discuss.elastic.co/t/openshift-problem-with-logstash-in-other-server/316157/1 "2022-10-09T19:06:08Z")

</div>

`2022-10-09T19:03:48,320][WARN][logstash.outputs.elasticsearch][openshift1] Attempted to resurrect connection to dead ES instance, but got an error {:url=>"http://elastichttp2-n-turri-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com:80/", :exception=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :message=>"Elasticsearch Unreachable: [http://elastichttp2-n-turri-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com:80/][Manticore::ConnectTimeout] Connect to elastichttp2-n-turri-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com:80 [elastichttp2-n-turri-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com/18.219.121.107, elastichttp2-n-turri-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com/18.119.15.249] failed: connect timed out"}`

this is host is open and response on browser

`http://elastichttp2-n-turri-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com`

```auto
{
  "name" : "elasticsearch-674bc84bfc-x87pm",
  "cluster_name" : "docker-cluster",
  "cluster_uuid" : "DdZD27mcTg2G3SAAyBJiKw",
  "version" : {
    "number" : "7.16.2",
    "build_flavor" : "default",
    "build_type" : "docker",
    "build_hash" : "2b937c44140b6559905130a8650c64dbd0879cfb",
    "build_date" : "2021-12-18T19:42:46.604893745Z",
    "build_snapshot" : false,
    "lucene_version" : "8.10.1",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}

```

my logstash config file

```auto
input {
  file {

    path => ["/logstash_dir/P2/*.*"]
    
    
    start_position => "beginning"
  }
}

output {
    if " ERROR " in [message] {
		elasticsearch {
			hosts => ["elastichttp2-n-turri-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com:80"]
			index => "errori_p2"
		}
		
		
    }
    
		stdout { codec => rubydebug }
}

```

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [October 9, 2022, 8:27pm UTC](https://discuss.elastic.co/t/openshift-problem-with-logstash-in-other-server/316157/2 "2022-10-09T20:27:04Z")

</div>

Can you `curl` from the logstash host to elasticsearch directly?

From the logstash host ... not a browser

`curl http://elastichttp2-n-turri-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com:80`

The error indicates a connectivity issues between the logstash host and your elasticsearch endpoint.

---

<div class="post-metadata">

**Author:** ![Nikolas1306](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikolas1306/32/111507_2.png) [@Nikolas1306](https://discuss.elastic.co/u/Nikolas1306)\
**Post date:** [October 9, 2022, 9:48pm UTC](https://discuss.elastic.co/t/openshift-problem-with-logstash-in-other-server/316157/3 "2022-10-09T21:48:30Z")

</div>

> [@stephenb](#):
>
> curl [http://elastichttp2-n-turri-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com:80](http://elastichttp2-n-turri-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com:80)

yes sir

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/1/b1b9ec90195d378bd229d6af2f344d1cc0def7e5.png)

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [October 9, 2022, 10:01pm UTC](https://discuss.elastic.co/t/openshift-problem-with-logstash-in-other-server/316157/4 "2022-10-09T22:01:19Z")

</div>

You need to do this test from where your Logstash service is running.

Can you connect to the logstash container/server and run this curl from there?

---

<div class="post-metadata">

**Author:** ![Nikolas1306](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikolas1306/32/111507_2.png) [@Nikolas1306](https://discuss.elastic.co/u/Nikolas1306)\
**Post date:** [October 9, 2022, 10:21pm UTC](https://discuss.elastic.co/t/openshift-problem-with-logstash-in-other-server/316157/5 "2022-10-09T22:21:44Z")

</div>

hello yes is connect and now is ok

i think openshift have internal strange firewall

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/c/fcbb640726dc0c8e093eb5fbf5cc566d86937eea.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 6, 2022, 10:22pm UTC](https://discuss.elastic.co/t/openshift-problem-with-logstash-in-other-server/316157/6 "2022-11-06T22:22:13Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.